Hi guys,
You know, _all field is deprecated. I wonder, how is still full-text search provide by ElasticSearch? The _all field was providing full-text search.
Is this not that right?
Hi guys,
You know, _all field is deprecated. I wonder, how is still full-text search provide by ElasticSearch? The _all field was providing full-text search.
Is this not that right?
We don't need anymore to index a fake _all field to provide the same feature.
Ok, I understand but how?
Any different field, maybe _source?
IIRC it's similar to running a multisearch query on all indexed fields but booleans.
Thanks @dadoonet for your answers.
In this case, why I need to enable _all field?
Why do I use custom field?
Who told you that you must enable _all field?
No, I know, it's not mandatory. I mean that there is no valid reason for using the field if I do understand correctly. Similarly custom all field, there is no valid reason for using it. What's provide custom all field when I use it? In which situations, why should I use it?
It's deprecated. Just don't use it.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
© 2020. All Rights Reserved - Elasticsearch
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.