We briefly discussed on IRC the phenomenon where when performing a
top_children query in a paginated fashion (using "from" and "size"
params to paginate), it's possible that the same result document may
appear in multiple pages. You indicated that this is a known issue
with top_children, and that increasing the "factor" would help
alleviate duplication.
My question is whether this is considered a bug (and thus slated for a
fix at some point) or more of an irreducible fact about the way
top_children works. I'm mostly just trying to determine whether our
application needs to be robust around potential duplication in the
long run.
Good question :), thats the state currently, I need to spend some time
thinking about ti to see if it can be fixed or thats simply the case with
top_children...
We briefly discussed on IRC the phenomenon where when performing a
top_children query in a paginated fashion (using "from" and "size"
params to paginate), it's possible that the same result document may
appear in multiple pages. You indicated that this is a known issue
with top_children, and that increasing the "factor" would help
alleviate duplication.
My question is whether this is considered a bug (and thus slated for a
fix at some point) or more of an irreducible fact about the way
top_children works. I'm mostly just trying to determine whether our
application needs to be robust around potential duplication in the
long run.
On Thu, Mar 29, 2012 at 10:10, Shay Banon kimchy@gmail.com wrote:
Good question :), thats the state currently, I need to spend some time
thinking about ti to see if it can be fixed or thats simply the case with
top_children...
We briefly discussed on IRC the phenomenon where when performing a
top_children query in a paginated fashion (using "from" and "size"
params to paginate), it's possible that the same result document may
appear in multiple pages. You indicated that this is a known issue
with top_children, and that increasing the "factor" would help
alleviate duplication.
My question is whether this is considered a bug (and thus slated for a
fix at some point) or more of an irreducible fact about the way
top_children works. I'm mostly just trying to determine whether our
application needs to be robust around potential duplication in the
long run.
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.