On 10 August 2015 at 12:16, Gunnar Morling <gunnar(a)hibernate.org> wrote:
> With these new types,backwards compatibility is a non-issue. So
unless
> someone makes a strong case for needing these as String in the index,
> what about we drop some complexity?
ElasticSearch uses Strings for transferring dates in JSON structures
(see
https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-d...).
So for that backend we'll need String-mapping field bridges (and we'd
even have to ignore/override/flag as error the user's setting for
numeric mapping).
Ok that sounds like another good reason to not provide a user option
to choose the encoding type, and we'll make appropriate choices.
Sanne