[
https://issues.apache.org/jira/browse/SOLR-13283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787925#comment-16787925
]
Munendra S N edited comment on SOLR-13283 at 3/8/19 2:24 PM:
-------------------------------------------------------------
[~superman369]
If understand correctly, \{!terms} is a special case where you would want only
terms specified should be returned in facet response along with count.
Until recently, none of the facet field features used to work on this. In
SOLR-13156, facet sorting support has been added. Since, in some cases terms
might need to be sorted by count. Also, that it supported
back-compatibility(sorted only when facet.sort)
I would like to understand as already required terms are specified what is the
usecase to restrict the terms in facet response? Similar explanation goes for
offset too.
There maybe a case of mincount support, where \{!terms} could be used for
exists functionality with cardinality greater than 1(For example, terms with
greater than equal to given count)
Also, Should \{!terms} support other facet field features like missing, exists
and etc
I think, most of features are not required here. Also, \{!terms} format should
be covered in documentation with set of features supported for this format
was (Author: munendrasn):
[~superman369]
If understand correctly, \{!terms} is a special case where you would want only
terms specified should be returned in facet response along with count.
Until recently, none of the facet field features used to work on this. In
SOLR-13156, facet sorting support has been added. Since, in some cases terms
might need to be sorted by count. Also, that it supported
back-compatibility(sorted only when facet.sort)
I would like to understand as already required terms are specified what is the
usecase to restrict the terms in facet response? Similar explanation goes for
offset too.
There maybe a case of mincount support, where \{!terms} could be used for
exists functionality with cardinality greater than 1(For example, terms with
greater than equal to given count)
Also, Should
{!terms} support other facet field features like missing, exists and etc
I think, most of features are not required here. Also, \{!terms}
format should be covered in documentation with set of features supported for
this format
> when facet with certain terms via {!terms}, facet.limit, facet.offset does
> not work
> -----------------------------------------------------------------------------------
>
> Key: SOLR-13283
> URL: https://issues.apache.org/jira/browse/SOLR-13283
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Facet Module
> Affects Versions: 7.7
> Reporter: superman369
> Priority: Major
>
> h4. I do a test in solr7.7. Limiting field facet with certain terms via
> \{!terms} is work use facet.sort=count, but facet.limit, facet.offset does
> not work. What's wrong?
> h4. for example:
> facet.field=\{!terms='1453,1452,1248'}location.authorIds&facet=true&facet.limit=1&facet.offset=1,
> facet result : "location.authorIds" has 3 items. I think it should have
> one item.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
