What's required on a field to make it sortable?
What's optional on a field when you want it sortable that might affect
how sorting works?
What's required on a field to make it sortable?
What's optional on a field when you want it sortable that might affect
how sorting works?
Every* non analyzed* type/field is sortable. Object comparison is used I
guess (date, long, string, int etc)
Every analyzed field can be sorted by _score because it's non sense to
sort an analyzed field : it has been split into tokens during analysis.
If you absolutly need an analyzed field to be sorted you can use *
multi-field*. It will store both analysed and non analysed representations
of the field. You'll then be able to sort by the non
analyzed representation.
Good luck,
--
Cordialement/Regards,
Louis GUEYE
linkedin http://fr.linkedin.com/in/louisgueye |
bloghttp://deepintojee.wordpress.com/
| twitter http://twitter.com/#!/lgueye
2012/2/6 Wes Plunk wes@wesandemily.com
What's required on a field to make it sortable?
What's optional on a field when you want it sortable that might affect
how sorting works?
© 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.