There are around 20,000 documents in the database - fairly small. This
specific query returns around 300 results.
I'm using a sort function that generates a hash off of a random string
combined with the document's id. It's entirely deterministic and should
only generate a different order if the salt changes.
When 'from" is set to zero and "size" is set to 10,000 (a number larger
than the total size of the index), then the first 10 documents show up in a
certain order. If I change "size" to 10, then I'd expect the documents to
show up in the same order as the first 10 documents from the query when
"size" was set to 10,000. As you can guess, it doesn't. The first 10
documents show up in completely different orders across the two searches.
Can anyone explain what's going on and how to fix it?
There are around 20,000 documents in the database - fairly small. This
specific query returns around 300 results.
I'm using a sort function that generates a hash off of a random string
combined with the document's id. It's entirely deterministic and should
only generate a different order if the salt changes.
When 'from" is set to zero and "size" is set to 10,000 (a number larger
than the total size of the index), then the first 10 documents show up in a
certain order. If I change "size" to 10, then I'd expect the documents to
show up in the same order as the first 10 documents from the query when
"size" was set to 10,000. As you can guess, it doesn't. The first 10
documents show up in completely different orders across the two searches.
Can anyone explain what's going on and how to fix it?
There are around 20,000 documents in the database - fairly small. This
specific query returns around 300 results.
I'm using a sort function that generates a hash off of a random string
combined with the document's id. It's entirely deterministic and should
only generate a different order if the salt changes.
When 'from" is set to zero and "size" is set to 10,000 (a number larger
than the total size of the index), then the first 10 documents show up in a
certain order. If I change "size" to 10, then I'd expect the documents to
show up in the same order as the first 10 documents from the query when
"size" was set to 10,000. As you can guess, it doesn't. The first 10
documents show up in completely different orders across the two searches.
Can anyone explain what's going on and how to fix it?
There are around 20,000 documents in the database - fairly small. This
specific query returns around 300 results.
I'm using a sort function that generates a hash off of a random string
combined with the document's id. It's entirely deterministic and should
only generate a different order if the salt changes.
When 'from" is set to zero and "size" is set to 10,000 (a number larger
than the total size of the index), then the first 10 documents show up in a
certain order. If I change "size" to 10, then I'd expect the documents to
show up in the same order as the first 10 documents from the query when
"size" was set to 10,000. As you can guess, it doesn't. The first 10
documents show up in completely different orders across the two searches.
Can anyone explain what's going on and how to fix it?
can you build a simple testcase / gist that reproduces the problem somehow?
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.