lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
Date Wed, 24 Dec 2014 19:22:13 GMT


Yonik Seeley commented on SOLR-6770:

bq. Actually , the usecase is, I'm trying to update a paramset and I made a typo in the name
. Now, I have two paramsets and the user thought he was right and he gets weird results

Urgg... does this mean that I can't just use "update" if I don't care if I'm overwriting a
previous one or not?  If that's true, I've mis-interpreted these parameters yet again.

This doesn't really protect against anything.  Someone could just as easily make a typo in
one of the parameters or one of the values.  The name isn't special.  This just makes it harder
for people not making typing errors.

For example, if I make a script to set a bunch of params periodically, I just want one way
to do it.  I don't want to have to do it one way the first time and then a different way every
subsequent time.

> Add/edit param sets and use them in Requests
> --------------------------------------------
>                 Key: SOLR-6770
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>            Reporter: Noble Paul
>            Assignee: Noble Paul
>             Fix For: Trunk
>         Attachments: SOLR-6770.patch, SOLR-6770.patch, SOLR-6770.patch
> Make it possible to define paramsets and use them directly in requests
> example
> {code}
> curl http://localhost:8983/solr/collection1/config/params -H 'Content-type:application/json'
 -d '{
> "create" : {"x": {
>               "a":"A val",
>               "b": "B val"}
>            },
> "update" : {"y": {
>                "x":"X val",
>                "Y": "Y val"}
>            },
> "modify" : {"y": {
>                "x":"X val modified"}
>            },
> "delete" : "z"
> }'
> #do a GET to view all the configured params
> curl http://localhost:8983/solr/collection1/config/params
> #or  GET with a specific name to get only one set of params
> curl http://localhost:8983/solr/collection1/config/params/x
> {code}
> This data will be stored in conf/params.json
> This is used requesttime and adding/editing params will not result in core reload and
it will have no impact on the performance 
> example usage http://localhost/solr/collection/select?useParams=x,y
> or it can be directly configured with a request handler as follows
> {code}
> <requestHandler name="/dump1" class="DumpRequestHandler" useParams="x"/>
> {code}
>  {{useParams}} specified in request overrides the one specified in {{requestHandler}}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message