You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Stefan Matheis (steffkes) (JIRA)" <ji...@apache.org> on 2011/06/17 22:38:47 UTC
[jira] [Created] (SOLR-2605) CoreAdminHandler, different Output
while 'defaultCoreName' is specified
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
Attachments: SOLR-2399-admin-cores-default.xml, SOLR-2399-admin-cores.xml
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-2605) CoreAdminHandler, different Output
while 'defaultCoreName' is specified
Posted by "Hoss Man (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-2605:
---------------------------
Attachment: SOLR-2605.patch
steffkes: your patch applies cleanly, but didn't compile -- it looks like you modified some files that weren't included in the patch?
based on the hoops it looked like you were having to jump through to track this, i looked at where/how/why were were throwing away the core name if it was the default core, and took a crack at just undo-ing that mess so that every core knows it's real and true name -- and only the CoreContainer worries about what the name of the default core is -- this only required two tweaks to tests (and one of those was to eliminate special hoops TestJmxIntegration was jumping through to get the right name if the core was the default!)
Once that was done, CoreAdminHandler seemed to return consistent name info in the status for every core, regardless of how many there were, or if a default name was in use. So then since i figured it would be handy, i added the defaultCoreName to the output when you get status for all cores (either a string or null if there is no default core name) and for good measure i also put an "isDefault" boolean in the status for each core.
try this out and see if does everything you need/want to make the UI go vroom ... like i said, all tests pass for me, but i don't want to commit w/o some review from miller -- this fix seems so easy i don't understand why the logic was reversed before, so i'm scared i may be missing something
> 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@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-2605) CoreAdminHandler, different Output
while 'defaultCoreName' is specified
Posted by "Otis Gospodnetic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450704#comment-13450704 ]
Otis Gospodnetic commented on SOLR-2605:
----------------------------------------
[~hossman_lucene@fucit.org] & [~steffkes] - 2 comments:
# was this really fixed in Solr 4.0 ALPHA? A colleague checked Solr 4.0 ALPHA for this and still saw a blank name=""
# is this back-portable to Solr 3.6.*? It seems 3.6.1 has the same bug.
> 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)
> Assignee: Hoss Man
> Priority: Minor
> Fix For: 4.0-ALPHA
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-2605) CoreAdminHandler, different Output
while 'defaultCoreName' is specified
Posted by "Stefan Matheis (steffkes) (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251418#comment-13251418 ]
Stefan Matheis (steffkes) commented on SOLR-2605:
-------------------------------------------------
obviously i had no idea where to change things correctly, was just trying to push this a bit forward :/ so i really appreciate your solution! Work's like a charm for me
> 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@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-2605) CoreAdminHandler, different Output
while 'defaultCoreName' is specified
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450965#comment-13450965 ]
Hoss Man commented on SOLR-2605:
--------------------------------
[~otis] not sure what to make of annecdotal evidence like that -- only took about 10 seconds for me to start up the 4.0-ALPHA example and confirm that /admin/cores returns "collection1" as the name of the only core (even if i point it at an old single-core style solr home dir so that the default hardcoded "SOLR_XML" logic kicks in) ... perhaps your colleague managed to create an actaul core with a name of "" ?
If you can reproduce, it's a new bug -- please file a new jira with the solr.xml, output of /admin/cores, and details on how you got solr into that state.
> 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)
> Assignee: Hoss Man
> Priority: Minor
> Fix For: 4.0-ALPHA
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-2605) CoreAdminHandler, different Output
while 'defaultCoreName' is specified
Posted by "Hoss Man (Commented) (JIRA)" <ji...@apache.org>.
[ 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@bester:~/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@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-2605) CoreAdminHandler, different Output
while 'defaultCoreName' is specified
Posted by "Stefan Matheis (steffkes) (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Matheis (steffkes) updated SOLR-2605:
--------------------------------------------
Attachment: SOLR-2605.patch
I have to admit, it's my first time .. if it's not usable - for whatever reason - just drop it.
For me, it was the only possibility to bring back the name - otherwise i will mess up the routing, i'm sure :D
> 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
>
>
> 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@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-2605) CoreAdminHandler, different Output
while 'defaultCoreName' is specified
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated SOLR-2605:
------------------------------
Fix Version/s: 4.0
> 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
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-2605) CoreAdminHandler, different Output
while 'defaultCoreName' is specified
Posted by "Otis Gospodnetic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451455#comment-13451455 ]
Otis Gospodnetic commented on SOLR-2605:
----------------------------------------
[~hossman_lucene@fucit.org] we were able to reproduce this with Solr 3.6.1. It this something you could backport, so the next 3.6.* release doesn't have this issue?
> 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)
> Assignee: Hoss Man
> Priority: Minor
> Fix For: 4.0-ALPHA
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-2605) CoreAdminHandler, different Output
while 'defaultCoreName' is specified
Posted by "Stefan Matheis (steffkes) (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254575#comment-13254575 ]
Stefan Matheis (steffkes) commented on SOLR-2605:
-------------------------------------------------
bq. Stefan: are you sure you had a clean build with my patch applied?
You're right .. i had some old stuff in {{solr/zoo_data}} which results in duplicate content. Looks still fine, ignore my last comment.
> 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@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-2605) CoreAdminHandler, different Output
while 'defaultCoreName' is specified
Posted by "Stefan Matheis (steffkes) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Matheis (steffkes) updated SOLR-2605:
--------------------------------------------
Attachment: SOLR-2399-admin-cores-default.xml
SOLR-2399-admin-cores.xml
> 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
> Attachments: SOLR-2399-admin-cores-default.xml, SOLR-2399-admin-cores.xml
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-2605) CoreAdminHandler, different Output
while 'defaultCoreName' is specified
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051950#comment-13051950 ]
Mark Miller commented on SOLR-2605:
-----------------------------------
Indeed - this has always been a bit ugly. Was kind of ease over best approach at the time if I remember right.
> 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
> Attachments: SOLR-2399-admin-cores-default.xml, SOLR-2399-admin-cores.xml
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-2605) CoreAdminHandler, different Output
while 'defaultCoreName' is specified
Posted by "Stefan Matheis (steffkes) (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252279#comment-13252279 ]
Stefan Matheis (steffkes) commented on SOLR-2605:
-------------------------------------------------
Not sure, where it comes from .. the {{clusterstate.json}} file looks like this, using the patch:
{code}{"collection1":{"shard1":{
"debian2:8983_solr_":{
"shard":"shard1",
"state":"active",
"core":"",
"collection":"collection1",
"node_name":"debian2:8983_solr",
"base_url":"http://debian2:8983/solr"},
"debian2:8983_solr_collection1":{
"shard":"shard1",
"leader":"true",
"state":"active",
"core":"collection1",
"collection":"collection1",
"node_name":"debian2:8983_solr",
"base_url":"http://debian2:8983/solr"}}}}{code}
Started with {{-DzkRun -Dcollection.configName=myconf -Dbootstrap_confdir=./solr/conf -Dsolr.environment=dev -Duser.timezone=UTC -DhostPort=8983 -Djetty.port=8983}}
> 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@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Resolved] (SOLR-2605) CoreAdminHandler, different Output
while 'defaultCoreName' is specified
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved SOLR-2605.
----------------------------
Resolution: Fixed
Assignee: Hoss Man
Committed revision 1330028.
> 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)
> Assignee: Hoss Man
> 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@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org