Greetings,

I wanted to discuss a bit about my update to the elasticgeo plugin.

The alias / short name function in the elasticgeo plugin does not seem to
be working from what I can tell, as reported in [GEOT-6575]
<https://osgeo-org.atlassian.net/browse/GEOT-6575>. I will break down what
is happening and what I plan to do here for transparency.

*Aliasing*
The aliasing feature expects you have already setup the alias in
elasticsearch. This might be considered "working properly", but seemed
misleading to me when you define your aliases in GeoServer, but it will
fail if the alias was not setup in elasticsearch.

I am considering having the plugin add the alias you define if it isn't
found, as well as change or remove the alias when you do that in the
plugin. I could keep track of the aliases we've added within the plugin to
ensure we only remove it if we added it. My main concern here is if this is
overstepping what the plugin should be doing.

If nothing else, I'll update documentation to explain this.

*Short Names*
As far as I can tell, this is an outdated elasticsearch concept which
was removed
in version 2.0
<https://www.elastic.co/guide/en/elasticsearch/reference/2.1/breaking_20_mapping_changes.html#_fields_cannot_be_referenced_by_short_name>.
I don't think it's possible anymore. Considering how old it is, I am
inclined to remove this functionality altogether and not support this
elasticsearch 1.x functionality. Aliases effectively accomplish the same
thing anyway.

I welcome any input here, especially regarding aliasing.

Cheers,
Travis
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to