[ https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256947#comment-14256947 ]
Noble Paul edited comment on SOLR-6770 at 12/23/14 12:54 PM: ------------------------------------------------------------- bq.The singular "param" in "useParam" I'm still ambivalent about it. I shall make it useParams bq.These feels very rest-like... is there a reason we're not going more rest-like for the updates as well? This could have followed full REST. But, then, we have a lot of APIs schema/config which support only GET/POST. I wanted this to be fully consistent with those APIs. the verbs available are {{create}} ,{{update}},{{modify}} and {{delete}} I'm still open to renaming the verbs . was (Author: noble.paul): bq.The singular "param" in "useParam" I'm still ambivalent about it. I shall make it useParams bq.These feels very rest-like... is there a reason we're not going more rest-like for the updates as well? This could have followed full REST. But then we have a lot of APIs schema/config which support this format only GET/POST. I wanted this to be fully consistent with those APIs. the verbs available are {{create}} ,{{update}},{{modify}} and {{delete}} I'm still open to renaming the verbs . > Add/edit param sets and use them in Requests > -------------------------------------------- > > Key: SOLR-6770 > URL: https://issues.apache.org/jira/browse/SOLR-6770 > Project: Solr > Issue Type: Sub-task > Reporter: Noble Paul > Assignee: Noble Paul > Attachments: 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" : {"name" ,"x", > "params": { > "a":"A val", > "b": "B val"} > }, > "update" : {"name" ,"y", > "params": { > "x":"X val", > "Y": "Y val"} > }, > "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?useParam=x,y > or it can be directly configured with a request handler as follows > {code} > <requestHandler name="/dump1" class="DumpRequestHandler" useParam="x"/> > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org