It seems that the field names in JSON aren't turned into a dictionary, so
longer field names end up taking noticeably more space. Especially for compact
data, like documents that contain only integer and date fields.
What is the recommendation for handling this? It's easy enough to have client
code just serialize with short names ("a", "b", etc.), but then debugging
queries or writing them by hand becomes difficult. I think I can use index_name
on mapping, so that a document with field "a" could be indexed as field
"createdOn", for example. Then my queries become easier, right? Then it's just
the return values (_source) that has the short names.
Any guidance on this is appreciated.
Thank you.
-Michael
--
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 protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/178efdbf33094e00a6bcf1d22140a4e2%40CO1PR07MB331.namprd07.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.
