jira at apache
Apr 13, 2012, 1:55 PM
Post #3 of 4
(58 views)
Permalink
|
|
[jira] [Commented] (SOLR-2605) CoreAdminHandler, different Output while 'defaultCoreName' is specified
[In reply to]
|
|
[ https://issues.apache.org/jira/browse/SOLR-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253736#comment-13253736 ]
Hoss Man commented on SOLR-2605:
--------------------------------
Stefan: are you sure you had a clean build with my patch applied?
when i run...
{noformat}
java -DzkRun -Dcollection.configName=myconf -Dbootstrap_confdir=./solr/conf -Dsolr.environment=dev -Duser.timezone=UTC -DhostPort=8983 -Djetty.port=8983 -jar start.jar
{noformat}
I get...
{noformat}
hossman [at] beste:~/lucene/dev/solr$ curl "http://localhost:8983/solr/zookeeper?detail=true&path=%2Fclusterstate.json"
{"znode":{
"path":"/clusterstate.json","prop":{
"version":5,
"aversion":0,
"children_count":0,
"ctime":"Fri Apr 13 20:27:46 UTC 2012 (1334348866331)",
"cversion":0,
"czxid":12,
"dataLength":290,
"ephemeralOwner":0,
"mtime":"Fri Apr 13 20:45:41 UTC 2012 (1334349941866)",
"mzxid":207,
"pzxid":12},
"data":"{\"collection1\":{\"shard1\":{\"bester:8983_solr_collection1\":{\n \"shard\":\"shard1\",\n \"leader\":\"true\",\n \"state\":\"active\",\n \"core\":\"collection1\",\n \"collection\":\"collection1\",\n \"node_name\":\"bester:8983_solr\",\n \"base_url\":\"http://bester:8983/solr\"}}}}"},"tree":[{"data":{
"title":"/clusterstate.json","attr":{
"href":"zookeeper?detail=true&path=%2Fclusterstate.json"}}}]}
{noformat}
> CoreAdminHandler, different Output while 'defaultCoreName' is specified
> -----------------------------------------------------------------------
>
> Key: SOLR-2605
> URL: https://issues.apache.org/jira/browse/SOLR-2605
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Reporter: Stefan Matheis (steffkes)
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-2399-admin-cores-default.xml, SOLR-2399-admin-cores.xml, SOLR-2605.patch, SOLR-2605.patch
>
>
> The attached XML-Files show the little difference between a defined {{defaultCoreName}}-Attribute and a non existing one.
> Actually the new admin ui checks for an core with empty name to set single- / multicore-settings .. it's a quick change to count the number of defined cores instead.
> But, will it be possible, to get the core-name (again)? One of both attributes would be enough, if that makes a difference :)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene
|
