[
https://issues.apache.org/jira/browse/SOLR-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13870009#comment-13870009
]
Erik Hatcher commented on SOLR-5627:
------------------------------------
My initial thought is that this might be best done as a (custom?)
SearchComponent rather adding this additional complexity to
defaults/invariants/appends. Thoughts? I guess it really depends on how many
others desire this capability?
> Config should contains an "Invariants"-like section, that lets the user the
> choise between a list of options, for a specific param
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-5627
> URL: https://issues.apache.org/jira/browse/SOLR-5627
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Isaac Hebsh
> Priority: Minor
> Labels: config, invariants, solrconfig.xml
> Fix For: 4.7
>
> Attachments: SOLR-5627.patch
>
>
> We want to limit our clients, so they can specify a parameter to request
> handler, but it must be one of some known values.
> When multiple values of a same parameter are defined in {{invariants}}
> section, all of these values are added to the query. This behavior is usefull
> for multivalue params (like {{facet.field}}) but does nothing for params like
> {{rows}}.
> We suggest to add another section, let's call it {{locked-list-values}} (bad
> name...)
> {code:xml}
> <locked-list-values>
> <int name="rows">10</int>
> <int name="rows">50</int>
> <int name="rows">100</int>
> <int name="rows">200</int>
> </locked-list-values>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
