[
https://issues.apache.org/jira/browse/SOLR-12795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amrit Sarkar updated SOLR-12795:
--------------------------------
Attachment: SOLR-12795.patch
> Introduce 'limit' parameter in FacetStream.
> -------------------------------------------
>
> Key: SOLR-12795
> URL: https://issues.apache.org/jira/browse/SOLR-12795
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: streaming expressions
> Reporter: Amrit Sarkar
> Priority: Major
> Attachments: SOLR-12795.patch
>
>
> Let's look at an observation regarding "bucketSizeLimit" in facetStream; and
> how we interpret it as a "limit". Suppose for 3 nested facets,
> bucketSizeLimit = 10, we receive total 1000 rows. since bucketSizeLimit =
> limit; ONLY the first top-level facet value's count will be returned; out of
> 10*10*10, 1*1*10th rows will be fetched. And the behavior will be consistent
> for any bucketSizeLimit we set,
> How about we have a separate parameter "limit" other than "bucketSizeLimit"
> which can be set to any arbitrary number (though should be <
> bucketSizeLimit^no_of_nested_facets), and that limit can be said "500". In
> this way, we will have the true SQL limit feature in place in FacetStream.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
