Does lucene / es optimize (or is there a way to config) keyword fields that are guaranteed to have only numbers and only need equality filtering (for inverted-index, doc-values, term dictionary etc) ?
I remember _id has this optimization, so the number isn't stored as a string(number).
Meaning, if it stores them as strings, then it would be better to store as base64 or something similar to reduce the string size, right ?
I understand coerce but this has nothing to do with what I asked. I was interested in low level optimization, something like https://github.com/elastic/elasticsearch/issues/25957 but for fields and not just the _id.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.