"Title": "TPTest Scaling 10:3"
Guid is not one of the supported data
As a result guid by default is indexed as string where dashes '-' are used
to break the long string into terms.
Search and aggregations will produce less than desired results unless the
Id field is mapped as not analysed.
Alternative is to strip off the dashes from the document, but such approach
will require custom serialization/de-serialization for the Guid data-type
in .Net using popular json parser http://james.newtonking.com/json.
The challenge is that Guid is widely used in our application and field name
is not always 'Id' and mapping every guid has proven quite time consuming
and in case of a missed mapping the data needs to be re-indexed.
Is there a less effort consuming approach?
Are there plans to support guid as core type?
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/bee7866e-2c0a-4ae1-9b48-0b17da2931ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.