Closed hokieg3n1us closed 6 years ago
Thanks for reporting this. The update to fix the issue is now committed and will be included in the next release. With the update you can click "Configure Elasticsearch fields" on the GeoServer layer configuration page (see docs), which will include fields added to the index after layer creation. If you're able to test please report back if there are still issues.
Included in 2.13.0 release
Currently, using ElasticGeo, it seems that whenever we create a mapping change on the index the store is referencing, we have to delete the layer and recreate it for those new fields in Elasticsearch to be recognized. It'd be nice to have even a refresh button on a layer to trigger an update to the attributes by reaching out to the mapping API.