Greetings,

I wanted to discuss here some proposed changes to the elasticgeo plugin
related to handling multiple valid date formats, as reported in [GEOT-6577]
<https://osgeo-org.atlassian.net/browse/GEOT-6577>.

As I've mentioned in the ticket, the core reason this issue is happening is
that the DataStore expects there to be just one valid date format, and that
is what it will use for the attribute. Elasticsearch is not as strict, and
permits mappings of multiple valid date formats for an index, meaning we
can get data with different date formats for the same attribute.

To allow this functionality, I plan to change the dateFormat to a List of
String objects, and rename it to validDateFormats. When reading the
feature, just iterate through the List looking for a date format which
matches the data value. When the data store is parsing the date format from
elastic, the List will be assigned to the format received, split on each ||.

I welcome input on the design here, if there's a more reasonable way to
accomplish this.

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

Reply via email to