You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Eric Pugh (Jira)" <ji...@apache.org> on 2022/02/13 11:49:00 UTC
[jira] [Assigned] (SOLR-15853) Managed ParamSets in the Solr Admin
[ https://issues.apache.org/jira/browse/SOLR-15853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Pugh reassigned SOLR-15853:
--------------------------------
Assignee: Eric Pugh
> Managed ParamSets in the Solr Admin
> -----------------------------------
>
> Key: SOLR-15853
> URL: https://issues.apache.org/jira/browse/SOLR-15853
> Project: Solr
> Issue Type: Improvement
> Components: Admin UI
> Affects Versions: 9.0
> Reporter: Eric Pugh
> Assignee: Eric Pugh
> Priority: Minor
> Time Spent: 50m
> Remaining Estimate: 0h
>
> ParamSets are a great way of organizing your parameters into an algorithem, and then referring to it by name. I've used it to drive A/B testing, or just to simplify my experimentation.
> https://nightlies.apache.org/solr/draft-guides/solr-reference-guide-main/request-parameters-api.html#viewing-request-parameters
> In SOLR-15834 we added documentation about the {{useParams}} parameter to the {{films}} example. This highlighted that while super powerful feature, the lack of a UI in the admin tool makes it very opaque feature to use. You have to be a JSON Jocky using Postman or a tool like that to manage this! I suspect most folks who embrace the ParamSets end up building a sepearate tool to manage this... (I was thinking about adding this to Quepid, and realized that wasn't helpful).
> It would be great if we had a UI that managed the {{params.json}} file in a user friendly way.l
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org