[
https://issues.apache.org/jira/browse/SOLR-15853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460716#comment-17460716
]
David Eric Pugh commented on SOLR-15853:
----------------------------------------
[~betulince] ;-) I don't know if we should just read params.json, update it
in the UI and post it back, or if we should actually have api's for managing
it?
> Managed ParamSets in the Solr Admin
> -----------------------------------
>
> Key: SOLR-15853
> URL: https://issues.apache.org/jira/browse/SOLR-15853
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Admin UI
> Affects Versions: main (9.0)
> Reporter: David Eric Pugh
> Priority: Minor
>
> 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-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
