[jira] [Commented] (SOLR-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14273576#comment-14273576
]
Noble Paul commented on SOLR-6607:
--
I got sucked into the bug fix mode. Let's track it in a separate issue
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Fix For: 5.0, Trunk
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H
'Content-type:application/json' -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b},
useParams:x
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
useParams:y ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14273017#comment-14273017
]
Alexandre Rafalovitch commented on SOLR-6607:
-
What happened with the *_meta_* implementation for the ground truth?
Now that */update* is in the explicit configuration, I cannot seem to find that
indicated when I do *curl
http://localhost:8983/solr/techproducts/config/requestHandler*
I talked about the *ground truth* in this issue on the November 28th. I can't
find what addresses it. Is there a different JIRA that I am missing perhaps?
Without the ground truth it is very hard to debug things.
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Fix For: 5.0, Trunk
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H
'Content-type:application/json' -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b},
useParams:x
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
useParams:y ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14266225#comment-14266225
]
ASF subversion and git services commented on SOLR-6607:
---
Commit 1649821 from [~noble.paul] in branch 'dev/trunk'
[ https://svn.apache.org/r1649821 ]
SOLR-6801 addressing test failures, SOLR-6607 supporting all initArgs for
requesthandlers
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Fix For: 5.0, Trunk
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H
'Content-type:application/json' -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b},
useParams:x
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
useParams:y ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14266260#comment-14266260
]
ASF subversion and git services commented on SOLR-6607:
---
Commit 1649826 from [~noble.paul] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1649826 ]
SOLR-6801 addressing test failures, SOLR-6607 supporting all initArgs for
requesthandlers
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Fix For: 5.0, Trunk
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H
'Content-type:application/json' -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b},
useParams:x
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
useParams:y ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14241490#comment-14241490
]
Yonik Seeley commented on SOLR-6607:
You gave a good example of what the API looks like, but not so much what it
does.
Does it work in solr-cloud mode? In stand-alone mode?
Are the changes persisted somehow in both of these modes? If so, what's the
mechanism. If not, is there a plan for that?
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Fix For: 5.0, Trunk
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b}
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
startup:lazy ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14241495#comment-14241495
]
Noble Paul commented on SOLR-6607:
--
bq.Does it work in solr-cloud mode? In stand-alone mode?
Both.
bq.Are the changes persisted somehow in both of these modes? If so, what's the
mechanism. If not, is there a plan for that?
In both cases changes are persisted.
for standalone node , it is written to the conf dir
for solrcloud it is written to zk
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Fix For: 5.0, Trunk
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b}
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
startup:lazy ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229062#comment-14229062
]
Noble Paul commented on SOLR-6607:
--
I don't think qt= matter here. handleSelect is not a problem either. It is
using the same handler that is defined somewhere using one of the existing
mechanisms
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Fix For: 5.0, Trunk
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b}
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
startup:lazy ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228838#comment-14228838
]
Alexandre Rafalovitch commented on SOLR-6607:
-
I don't have a terribly strong opinion on the specific setup. As long as it can
answer two questions easily:
1. What handlers do I actually have
2. Why do I have those specific handlers (where are they defined and whether
they override/are overriden).
The above proposal seems to cover those two questions.
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Fix For: 5.0, Trunk
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b}
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
startup:lazy ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228858#comment-14228858
]
Alexandre Rafalovitch commented on SOLR-6607:
-
Ugh, just realized. Does this also cover handleSelect=true and reports it (the
fourth location? actually even messier with qt=).
Also related: SOLR-6807 and SOLR-3346
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Fix For: 5.0, Trunk
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b}
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
startup:lazy ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228528#comment-14228528
]
Alexandre Rafalovitch commented on SOLR-6607:
-
I think it is very important to have unified way to get all the different
permutations of *ground truth*. Prior to these - exciting - new developments,
there was one place to find the ground truth - in solrconfig.xml. You could
grep the file and get everything you needed (well, except for admin ones, but
they were mentioned in the comments).
But now, we have a lot more handlers that are implicit plus the hardcoded ones
and the overlay ones. If there is no way to get all of the information
(including the source of the definition) in one place, there will be confusion
down the line. From users and - I suspect - tool writers.
So, I think a single end-point with parameters to differentiate the source
would be nice. The parameters could be ?source=all, source=implicit,
source=defined, source=overlay as well as status=active, status=overriden and
status=disabled/inactive (maybe). By default, it would be source=all and
status=active. These two parameters would be included for each entry.
So, if I have _/selectAR_ in solrconfig.xml and it's also overriden in the
overlay then it will be returned as *source=overlay*, *status=active* when I
request with *source=all*, but as *source=defined*, *status=overriden* when I
request with *source=defined*.
Does it make sense?
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Fix For: 5.0, Trunk
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b}
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
startup:lazy ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228635#comment-14228635
]
Noble Paul commented on SOLR-6607:
--
how about adding extra information to the {{/config}} end point
example
{code}
/analysis/field: {
_meta_ : {
source : overlay, // alternatively, implicit,
solrconfig.xml
overrides : solrconfig.xml
}
startup: lazy,
name: /analysis/field,
class: solr.FieldAnalysisRequestHandler
}
{code}
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Fix For: 5.0, Trunk
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b}
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
startup:lazy ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228638#comment-14228638
]
Noble Paul commented on SOLR-6607:
--
bq.So, I think a single end-point with parameters to differentiate the source
would be nice
The objective pf {{/config}} endpoint is to give the definitive schema that is
in use now
For checking the overlay the endpoint is {{/config/overlay}}. Probably we can
add more end points for solrconfig.xml
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Fix For: 5.0, Trunk
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b}
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
startup:lazy ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14227642#comment-14227642
]
ASF subversion and git services commented on SOLR-6607:
---
Commit 1642141 from [~noble.paul] in branch 'dev/trunk'
[ https://svn.apache.org/r1642141 ]
SOLR-6607 Managing requesthandlers through API
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b}
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
startup:lazy ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14227648#comment-14227648
]
ASF subversion and git services commented on SOLR-6607:
---
Commit 1642143 from [~noble.paul] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1642143 ]
SOLR-6607 Managing requesthandlers through API
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b}
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
startup:lazy ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14227662#comment-14227662
]
ASF subversion and git services commented on SOLR-6607:
---
Commit 1642151 from [~noble.paul] in branch 'dev/trunk'
[ https://svn.apache.org/r1642151 ]
SOLR-6607 /config path should show overridden requesthandler
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b}
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
startup:lazy ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14227669#comment-14227669
]
ASF subversion and git services commented on SOLR-6607:
---
Commit 1642153 from [~noble.paul] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1642153 ]
SOLR-6607 /config path should show overridden requesthandler
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b}
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
startup:lazy ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14227675#comment-14227675
]
Alexandre Rafalovitch commented on SOLR-6607:
-
Would it be possible - if not done already - for when these combined request
handlers returned, there is a synthetic attribute which says whether they were
loaded from source, from overlay (only), or from overlay as an over-ride.
Having such flag will significantly simplify troubleshooting for both user and
Solr developer adding more features later.
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b}
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
startup:lazy ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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-6607) Managing requesthandlers through API
[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228070#comment-14228070
]
Noble Paul commented on SOLR-6607:
--
Currently , you can hit {{/config/overlay}} to know the request handlers
specified in overlay. And {{/config/requestHandler}} can give you all request
handlers registered in the core.
Currently , there are three places a requesthandler can be loaded from
* registered in overlay
* registered in solrconfig.xml
* implicit ones , registered in code
And the priority is in that order .
However, we are planning to add a new a new endpoint
{{/requesthandlername/_meta}} which gives the details of the requesthandler .
Do you think it is necessary to know from where it is loaded in the {{/config}}
end point itself ?
Managing requesthandlers through API
Key: SOLR-6607
URL: https://issues.apache.org/jira/browse/SOLR-6607
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
Assignee: Noble Paul
Fix For: 5.0, Trunk
Attachments: SOLR-6607.patch
The concept of solrconfig editing is split into multiple pieces . This issue
is about registering components and uploading binaries through an API.
This supports multiple operations
* commands 'create-requesthandler',
update-requesthandler,delete-requesthandler which can set the
configuration of a component . This configuration will be saved inside the
configoverlay.json
The components has to be available in the classpath of all nodes.
example for registering a component
{code}
curl http://localhost:8983/solr/collection1/config -H -d '{
create-requesthandler : {name: /mypath ,
class:com.mycomponent.ClassName
,
defaults:{x:y , a:b}
},
update-requesthandler :{name: /mypath ,
class:com.mycomponent.ClassName ,
startup:lazy ,
defaults:{x:y , a:b}
},
delete-requesthandler :/mypath
}'
{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
