[
https://issues.apache.org/jira/browse/SOLR-17570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-17570:
--------------------------------
Description:
Claim: Someone using cursorMark (deep paging) probably doesn't care about
numFound at all, and thus could set minExactCount=0 param. And if they want to
know, they either find out on the first page straight away (nextCursorMark is
absent) or failing that, it could send a query purely to ascertain what
numFound is if it doesn't want to page to the end.
I see no test with both functionalities together. I think it should work this
way by default. I tried this with a quick hack using DistribCursorPagingTest
and it triggered an assertion in
{{org.apache.solr.search.SolrIndexSearcher#sortDocSet}} that didn't need to be
there -- it can be removed. The functionality worked.
was:
Claim: Someone using cursorMark (deep paging) probably doesn't care about
numFound at all. And if they want to know, they either find out on the first
page straight away (nextCursorMark is absent) or failing that, it could send a
query purely to ascertain what numFound is if it doesn't want to page to the
end.
I see no test with both functionalities together. I think it should work this
way by default. I tried this with a quick hack using DistribCursorPagingTest
and it triggered an assertion in
{{org.apache.solr.search.SolrIndexSearcher#sortDocSet}} that didn't need to be
there -- it can be removed. The functionality worked.
> cursorMark should assume minExactCount=0
> ----------------------------------------
>
> Key: SOLR-17570
> URL: https://issues.apache.org/jira/browse/SOLR-17570
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Priority: Major
>
> Claim: Someone using cursorMark (deep paging) probably doesn't care about
> numFound at all, and thus could set minExactCount=0 param. And if they want
> to know, they either find out on the first page straight away (nextCursorMark
> is absent) or failing that, it could send a query purely to ascertain what
> numFound is if it doesn't want to page to the end.
> I see no test with both functionalities together. I think it should work
> this way by default. I tried this with a quick hack using
> DistribCursorPagingTest and it triggered an assertion in
> {{org.apache.solr.search.SolrIndexSearcher#sortDocSet}} that didn't need to
> be there -- it can be removed. The functionality worked.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
