[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14362477#comment-14362477
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1666817 from [~yo...@apache.org] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1666817 ]
SOLR-6770: reformat - fix bad indentation and funky formatting
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
Fix For: 5.0, 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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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}}
A more realistic example
{code}
curl http://localhost:8983/solr/collection1/config/params -H
'Content-type:application/json' -d '{
set:{query:{
defType:edismax,
q.alt:*:*,
rows:10,
fl:*,score },
facets:{
facet:on,
facet.mincount: 1
},
velocity:{
wt: velocity,
v.template:browse,
v.layout: layout
}
}
}
{code}
and use all of them directly is a requesthandler
{code:xml}
requestHandler name=/browse class=solr.SearchHandler
useParams=query,facets,velocity,browse/
{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
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14362474#comment-14362474
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1666816 from [~yo...@apache.org] in branch 'dev/trunk'
[ https://svn.apache.org/r1666816 ]
SOLR-6770: reformat - fix bad indentation and funky formatting
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
Fix For: 5.0, 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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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}}
A more realistic example
{code}
curl http://localhost:8983/solr/collection1/config/params -H
'Content-type:application/json' -d '{
set:{query:{
defType:edismax,
q.alt:*:*,
rows:10,
fl:*,score },
facets:{
facet:on,
facet.mincount: 1
},
velocity:{
wt: velocity,
v.template:browse,
v.layout: layout
}
}
}
{code}
and use all of them directly is a requesthandler
{code:xml}
requestHandler name=/browse class=solr.SearchHandler
useParams=query,facets,velocity,browse/
{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
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14278785#comment-14278785
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1652134 from [~noble.paul] in branch 'dev/trunk'
[ https://svn.apache.org/r1652134 ]
SOLR-6770 mask the useParams aftger expanding it
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
Fix For: 5.0, 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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14278869#comment-14278869
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1652155 from [~noble.paul] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1652155 ]
SOLR-6770 accidentally commented out a test
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
Fix For: 5.0, 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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14278814#comment-14278814
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1652137 from [~noble.paul] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1652137 ]
SOLR-6770 mask the useParams after expanding it
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
Fix For: 5.0, 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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14278863#comment-14278863
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1652153 from [~noble.paul] in branch 'dev/trunk'
[ https://svn.apache.org/r1652153 ]
SOLR-6770 accidentally commented out a test
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
Fix For: 5.0, 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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14278883#comment-14278883
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1652159 from [~noble.paul] in branch 'dev/branches/lucene_solr_5_0'
[ https://svn.apache.org/r1652159 ]
SOLR-6770 mask the useParams after expanding it
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
Fix For: 5.0, 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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14279861#comment-14279861
]
Noble Paul commented on SOLR-6770:
--
The current trunk implements the /browse feature using useParams
I'll post another real world example
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
Fix For: 5.0, 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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14279689#comment-14279689
]
Alexandre Rafalovitch commented on SOLR-6770:
-
Do we have a real example of this, rather than a/b/c? I am not entirely sure
how to use/test these in the end.
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
Fix For: 5.0, 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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14274942#comment-14274942
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1651308 from [~noble.paul] in branch 'dev/trunk'
[ https://svn.apache.org/r1651308 ]
SOLR-6770 Optimize tests to avoid duplicate RE[BST calls
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
Fix For: 5.0, 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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14275008#comment-14275008
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1651316 from [~noble.paul] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1651316 ]
SOLR-6770 Optimize tests to avoid duplicate REST calls
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
Fix For: 5.0, 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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264660#comment-14264660
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1649542 from [~noble.paul] in branch 'dev/trunk'
[ https://svn.apache.org/r1649542 ]
SOLR-6770 wrong file name in standalone mode
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
Fix For: 5.0, 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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264663#comment-14264663
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1649543 from [~noble.paul] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1649543 ]
SOLR-6770 wrong file name in standalone mode
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
Fix For: 5.0, 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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264695#comment-14264695
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1649551 from [~noble.paul] in branch 'dev/trunk'
[ https://svn.apache.org/r1649551 ]
SOLR-6770 Added testcase for standalone mode and fixed a reload bug
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
Fix For: 5.0, 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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264701#comment-14264701
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1649553 from [~noble.paul] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1649553 ]
SOLR-6770 Added testcase for standalone mode and fixed a reload bug
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
Fix For: 5.0, 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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14262561#comment-14262561
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1648847 from [~noble.paul] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1648847 ]
SOLR-6770: Add/edit param sets and use them in Requests
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
Fix For: 5.0, 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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14262137#comment-14262137
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1648689 from [~noble.paul] in branch 'dev/trunk'
[ https://svn.apache.org/r1648689 ]
SOLR-6801 more tests , SOLR-6770 refactored code around
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
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 '{
set : {x: {
a:A val,
b: B val}
},
set : {y: {
x:X val,
Y: Y val}
},
update : {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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14259062#comment-14259062
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1647962 from [~noble.paul] in branch 'dev/trunk'
[ https://svn.apache.org/r1647962 ]
SOLR-6770 changed command names to set, update
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
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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258911#comment-14258911
]
David Smiley commented on SOLR-6770:
+1
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
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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258117#comment-14258117
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1647748 from [~noble.paul] in branch 'dev/trunk'
[ https://svn.apache.org/r1647748 ]
SOLR-6770 Add/edit param sets and use them in requests
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, 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}
--
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
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258301#comment-14258301
]
Yonik Seeley commented on SOLR-6770:
Do we really need separate create and update actions? (and I was initially
confused about the difference between update and modify).
create doesn't seem so useful if update can do the same thing without
erroring if it already exists.
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
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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258374#comment-14258374
]
Noble Paul commented on SOLR-6770:
--
I have separate commands to avoid accidental overwrite. It is just to idiot
proof the system.
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
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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258381#comment-14258381
]
Yonik Seeley commented on SOLR-6770:
bq. I have separate commands to avoid accidental overwrite. It is just to idiot
proof the system.
I understand the rational, but I just wonder if it makes it easier or harder to
use in practice. This actually creates another mode of failure.
As an example, a common idiot/newbie mistake to make may now be:
1) send in a create command
2) try it out... yay, it works.
3) modify the command a bit and send it in again... failure? Arg... I have to
use a *different* command if it already exists?
Look at our APIs for adding documents... by default it's a create that replaces
any existing document.
Obviously, the right default semantics depend on the API and expected
use-cases. But I can't think of realistic use-cases when I want to add a param
set but I want it to fail if it already exists.
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
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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258438#comment-14258438
]
Noble Paul commented on SOLR-6770:
--
bq. But I can't think of realistic use-cases when I want to add a param set but
I want it to fail if it already exists.
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 is confused.
To be honest I can go either way
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
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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258443#comment-14258443
]
ASF subversion and git services commented on SOLR-6770:
---
Commit 1647829 from [~noble.paul] in branch 'dev/trunk'
[ https://svn.apache.org/r1647829 ]
SOLR-6770 fixing test failures
http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/2013/
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
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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258467#comment-14258467
]
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: https://issues.apache.org/jira/browse/SOLR-6770
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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258472#comment-14258472
]
Alexandre Rafalovitch commented on SOLR-6770:
-
Is there a result status (created, updated, deleted, failed, etc)? Might be a
way to unify the API yet show the difference in treatment.
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
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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258486#comment-14258486
]
David Smiley commented on SOLR-6770:
+1 to this point. Like with documents, I want to add if not there or update if
it is there. Perhaps the response might let me know what happened if I'm
curious.
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
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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258655#comment-14258655
]
Noble Paul commented on SOLR-6770:
--
OK, So let's make the commands
* {{set}} : create if does not exist. replace if exists
* {{update}} : merge the map with new values
* {{delete}}
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
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
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256927#comment-14256927
]
Yonik Seeley commented on SOLR-6770:
The singular param in useParam sounds a little weird since you're actually
specifying a set of params. How about useParams?
{code}
#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}
These feels very rest-like... is there a reason we're not going more rest-like
for the updates as well?
{code}
curl http://localhost:8983/solr/collection1/config/params/x -d '
{
a:A val,
b: B val
}
'
OR...
curl -XPUT http://localhost:8983/solr/collection1/config/params -d '
{
x : {
a:A val,
b: B val
}
}
'
{code}
I suppose it's because of the desire to be able to specify create vs update
(and I assume the latter changes a param set rather than overwrites it?).
Is there another resty way to specify that distinction?
Even if we keep updates of the form:
{code}
create : {name ,x,
params: {
a:A val,
b: B val}
{code}
We could actually eliminate the other names of name and params with a
structure like:
{code}
create : {
x: {
a:A val,
b: B val
}
}
{code}
Which seems a little more straightforward.
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
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256947#comment-14256947
]
Noble Paul commented on SOLR-6770:
--
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
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256957#comment-14256957
]
Noble Paul commented on SOLR-6770:
--
bq.We could actually eliminate the other names of name and params with a
structure like:
I actually started with that . I am worried how to support any metadata if I
wish to add them in future ?
{code}
create : {
x: {
: {meta-key1:val}
a:A val,
b: B val
}
}
{code}
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
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256959#comment-14256959
]
Noble Paul commented on SOLR-6770:
--
OK , I'll change the syntax and post a new patch
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
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255629#comment-14255629
]
Noble Paul commented on SOLR-6770:
--
yes we can change the key
specifying the content type can be made optional
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
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,
val: {
a:A val,
b: B val}
},
update : {name ,y,
val: {
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?useParams=x,y
or it can be directly configured with a request handler as follows
{code}
requestHandler name=/dump1 class=DumpRequestHandler useParams=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
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255276#comment-14255276
]
Shalin Shekhar Mangar commented on SOLR-6770:
-
This looks nice!
# Can we please use params or value instead of val in the json commands?
# Specifying the content-type would be optional, right?
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
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,
val: {
a:A val,
b: B val}
},
update : {name ,y,
val: {
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?useParams=x,y
or it can be directly configured with a request handler as follows
{code}
requestHandler name=/dump1 class=DumpRequestHandler useParams=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
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14254852#comment-14254852
]
Alexandre Rafalovitch commented on SOLR-6770:
-
Would these be *default* params only? Or compulsory/added params as well?
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
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
val: {
a:A val,
b: B val}
},
update : {name ,y
val: {
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/paramsets.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
or it can be directly configured with a request handler as follows
{code}
requestHandler name=/dump1 class=DumpRequestHandler useParams=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
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14254883#comment-14254883
]
Noble Paul commented on SOLR-6770:
--
These are shorthands for request params . it is equivalent to {{defaults}} but
the component will not have access to these during {{init()}} . So it is purely
a request time construct
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
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
val: {
a:A val,
b: B val}
},
update : {name ,y
val: {
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/paramsets.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
or it can be directly configured with a request handler as follows
{code}
requestHandler name=/dump1 class=DumpRequestHandler useParams=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
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14254914#comment-14254914
]
Alexandre Rafalovitch commented on SOLR-6770:
-
What about in your second example where you are defining them on the
requestHandler itself? Does it become just a second set of default to layer on
top of the set defined in-place. What order does it apply in if both are
present?
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
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
val: {
a:A val,
b: B val}
},
update : {name ,y
val: {
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/paramsets.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
or it can be directly configured with a request handler as follows
{code}
requestHandler name=/dump1 class=DumpRequestHandler useParams=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
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14254918#comment-14254918
]
Noble Paul commented on SOLR-6770:
--
The second option is an shorthand if you don't want to pass it with every
request and again those parameters will not be available during init()
The construct allows you to apply more than one param sets. I can say
{{useParams=x,y,z}} and in that case all are applied in the order they are
specified (the way defaults are applied currently) . If the request has a
{{useParams}} value , the one specified in the requestHandler is ignored.
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
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
val: {
a:A val,
b: B val}
},
update : {name ,y
val: {
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/paramsets.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}
--
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
[jira] [Commented] (SOLR-6770) Add/edit param sets and use them in Requests
[
https://issues.apache.org/jira/browse/SOLR-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14251655#comment-14251655
]
David Smiley commented on SOLR-6770:
+1 Nice! Looking forward to this.
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
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
val: {
a:A val,
b: B val}
},
update : {name ,y
val: {
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/paramsets.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
or it can be directly configured with a request handler as follows
{code}
requestHandler name=/dump1 class=DumpRequestHandler useParams=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
