[
https://issues.apache.org/jira/browse/SOLR-9682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762558#comment-16762558
]
Mikhail Khludnev edited comment on SOLR-9682 at 2/8/19 7:41 AM:
----------------------------------------------------------------
[[email protected]], I've got your point. I'll keep {{domain.filer.param}}
intact.
Can you consider my point about having mandatory singular parameter reference?
Does it make sense after all?
If it does we can think about introducing {{domain.filer.reqParam}} or treat as
old good nested referencing syntax as mandatory single. Here's how it might
seem in the ref guide
{quote}
The value of `filter` can be a single query to treat as a filter, or a JSON
list of filter queries. Each query can be:
* a string containing a query in Solr query syntax `"color:blue"`
* a reference to a request parameter containing Solr query syntax, of the form:
`\{param : <request_param_name>}`.
The referred parameter might absent or has many values. In the former case, no
filter is applied, and no error is raised. In the latter case all filters
parsed from these values are intersected.
* a string containing a reference in nested Solr query syntax:
`"\{!v=$color_filter}"`. It requires that the exactly one such parameter is
provided in request, otherwise it causes an error.
{quote}
Note. that's how it's done in SOLR-13232. It impact really old piece of query
dereferencing, so far I don't see test failures, and I suppose it improves
sanity since now these refs works like {{\{!v=$color_filter[0]}}} which might
yield some surprises from repeating param order.
was (Author: mkhludnev):
[[email protected]], I've got your point. I'll keep {{domain.filer.param}}
intact.
Can you consider my point about having mandatory singular parameter reference?
Does it make sense after all?
If it does we can think about introducing {{domain.filer.reqParam}} or treat as
old good nested referencing syntax as mandatory single. Here's how it might
seem in the ref guide
{quote}
The value of `filter` can be a single query to treat as a filter, or a JSON
list of filter queries. Each query can be:
* a string containing a query in Solr query syntax `"color:blue"`
* a reference to a request parameter containing Solr query syntax, of the form:
`\{param : <request_param_name>}`.
The referred parameter might absent or has many values. In the former case, no
filter is applied, and no error is raised. In the latter case all filters
parsed from these values are intersected.
* a string containing a reference in nested Solr query syntax:
`"\{!v=$color_filter}"`. It requires that the exactly one such parameter is
provided in request, otherwise it causes an error.
{quote}
Note. that's how it's done in the last patch in SOLR-12330. It impact really
old piece of query dereferencing, so far I don't see test failures, and I
suppose it improves sanity since now these refs works like
{{\{!v=$color_filter[0]}}} which might yield some surprises from repeating
param order.
> Ability to specify a query with a parameter name (in facet filter)
> ------------------------------------------------------------------
>
> Key: SOLR-9682
> URL: https://issues.apache.org/jira/browse/SOLR-9682
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Facet Module
> Reporter: Yonik Seeley
> Assignee: Yonik Seeley
> Priority: Major
> Fix For: 6.4, 7.0
>
> Attachments: SOLR-9682.patch
>
>
> Currently, "filter" only supports query strings (examples at
> http://yonik.com/solr-json-request-api/ )
> It would be nice to be able to reference a param that would be parsed as a
> lucene/solr query. Multi-valued parameters should be supported.
> We should keep in mind (and leave room for) a future "JSON Query Syntax" and
> chose labels appropriately.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
