The documentation suggests using low cardinality field(s) for index sorting. We often search documents with some low cardinality ID (like site or org) and then with timestamp. Does it make sense to include timestamp in the mix? I am paying a little bit overhead for the write with "index sorting".…

Index sorting on a field is good for 2 things: to reduce disk usage and speed up queries with sort on this field. Disk space is reduced because we can efficiently compress the same values, but this would not help timestamp field, as I expect this field will have all unique values. So there are no …

Discuss the Elastic Stack

Does it make sense to add timestamp in "index sorting"?

Elastic Stack Elasticsearch

linkerc October 13, 2021, 6:05pm 3

Thanks. I will remove it for our deployment.

Topic		Replies	Views
Elastic Search Sorting takes time between 4-5 secs Elasticsearch	3	2763	July 6, 2017
Sort by _timestamp not working Elasticsearch	5	2894	July 6, 2017
Will index sorting improve performance on fuzzy queries? Elasticsearch	1	369	June 7, 2018
Sorting date fields Elasticsearch	5	357	July 6, 2017
ES 1.2.1 sort by _timestamp Elasticsearch	8	636	July 6, 2017

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

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.

Does it make sense to add timestamp in "index sorting"?

Related topics