for comments - GEOMESA-233 adding scalding job to index attributes through geoserver UI

Still TODO - 
* create ticket for the TODO in the code
* error handling in UI for failed m/r jobs
* unit tests

Does cf need to be lazy?  Lazy uses a set-only-once pattern which might have a tiny bit of overhead.  I think I can see what value might be lazy.