It looks like Elastic Search is overriding my default mapping values when it
adds defaults dynamically.
I'm seeing ints being stored as longs and floats and double being stored as
string when using
client.admin().indices().create(createRequest)
Dates appear fine.
Here is part of the value used in createRequest.settings(value):
"trxamount":{"type":"double","boost":1}
Here is what I see in the logs:
trxamount":{"type":"string","index_name":"trxamount","index":"analyzed","store":"no","term_vector":"no","boost":1.0,"omit_norms":false,"omit_term_freq_and_positions":false}
I initially create an index using mappings, I don't provide all the fields
such term_vector omit_terms etc, so Elastic Search is dynamically adding
them later when I perform an index.
It looks like it is overriding my mappings.
I initially create an index using mappings, I don't provide all the fields
such term_vector omit_terms etc, so Elastic Search is dynamically adding
them later when I perform an index.
It looks like it is overriding my mappings.
Can you explain how you set the mappings in the API? You don't set them
through the settings on the createRequest, there is an API to put mappings,
or add mappings as part of the API to create an index. If you provide
explicit mappings, then elasticsearch should not override what you provided.
I initially create an index using mappings, I don't provide all the fields
such term_vector omit_terms etc, so Elastic Search is dynamically adding
them later when I perform an index.
It looks like it is overriding my mappings.
Can you explain how you set the mappings in the API? You don't set them
through the settings on the createRequest, there is an API to put mappings,
or add mappings as part of the API to create an index. If you provide
explicit mappings, then elasticsearch should not override what you provided.
I initially create an index using mappings, I don't provide all the
fields such term_vector omit_terms etc, so Elastic Search is dynamically
adding them later when I perform an index.
It looks like it is overriding my mappings.
Can you explain how you set the mappings in the API? You don't set them
through the settings on the createRequest, there is an API to put mappings,
or add mappings as part of the API to create an index. If you provide
explicit mappings, then elasticsearch should not override what you provided.
I initially create an index using mappings, I don't provide all the
fields such term_vector omit_terms etc, so Elastic Search is dynamically
adding them later when I perform an index.
It looks like it is overriding my mappings.
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.