[
https://issues.apache.org/jira/browse/SOLR-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett resolved SOLR-6050.
-------------------------------------
Resolution: Duplicate
I believe what was requested here was satisfied by SOLR-6152, released in Solr
8.9.
> Solr Admin Query UI: support initializing all fields from a Solr query string
> -----------------------------------------------------------------------------
>
> Key: SOLR-6050
> URL: https://issues.apache.org/jira/browse/SOLR-6050
> Project: Solr
> Issue Type: Improvement
> Components: Admin UI
> Affects Versions: 4.7.2
> Reporter: Gunnlaugur Thor Briem
> Priority: Minor
> Labels: javascript
>
> Make it easy to initialize (with a hyperlink) the Solr Admin UI query page
> with a given Solr query, to make “Open this query in Solr Admin Query UI”
> links.
> It is already *partly* possible to link to the Solr Admin UI query page with
> parameters to initialize the form fields, e.g.:
> http://localhost:8983/solr/#/mycore/query?q=foo&fq=bar:baz
> But this support is pretty limited. Main limitations:
> 1. Repeated parameters (e.g. {{fq=foo:bar&fq=baz:xyzzy}}) don't work.
> Workaround: convert them to a single parameter with + in front of each
> filter: {{fq=%21foo%3Abar%20%21baz%3Axyzzy}} — but of course that workaround
> yields a less convenient setup in the query page. Also doesn't work for all
> repeated fields, e.g. {{facet.field=foo%20baz}} is not valid in a Solr query.
> 2. feature-enabling checkboxes don't get checked (e.g. by {{facet=on}} and
> {{hl=on}})
> 3. Field-specific overrides (e.g. {{f.cat_id.facet.limit=37}}) are not
> captured — these could be placed in “Raw Query Parameters”
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
