[
https://issues.apache.org/jira/browse/SOLR-12394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Pugh updated SOLR-12394:
-----------------------------
Description:
NodeConfig has a property called managementPath config which doesn't appear to
serve any coherent function and is in fact documented in
[https://lucene.apache.org/solr/guide/7_3/format-of-solr-xml.html] as:
{quote}{{managementPath}}
Currently non-operational.
{quote}
The code appears to have been added initially in SOLR-695, and that ticket
appears to relate to an elimination of a special case for single core
configurations. It seems that this may have been an attempt to support single
cores that had no name (a legacy mode of operation I guess, but before my time)
and yet still allow such single core setups to later have additional cores
added?
So this ticket is a suggestion that we remove this configuration that allegedly
isn't working anyway, OR we make it work and give it good clear documentation
in code and in the ref guide so that folks don't have to waste a lot of time
figuring out what it does(n't do) to understand the code.
Attaching patch to remove it.
was:
NodeConfig has a property called managmentPath config which doesn't appear to
serve any coherent function and is in fact documented in
[https://lucene.apache.org/solr/guide/7_3/format-of-solr-xml.html] as:
{quote}{{managementPath}}
Currently non-operational.
{quote}
The code appears to have been added initially in SOLR-695, and that ticket
appears to relate to an elimination of a special case for single core
configurations. It seems that this may have been an attempt to support single
cores that had no name (a legacy mode of operation I guess, but before my time)
and yet still allow such single core setups to later have additional cores
added?
So this ticket is a suggestion that we remove this configuration that allegedly
isn't working anyway, OR we make it work and give it good clear documentation
in code and in the ref guide so that folks don't have to waste a lot of time
figuring out what it does(n't do) to understand the code.
Attaching patch to remove it.
Summary: Remove managementPath (was: Remove managmentPath )
> Remove managementPath
> ----------------------
>
> Key: SOLR-12394
> URL: https://issues.apache.org/jira/browse/SOLR-12394
> Project: Solr
> Issue Type: Improvement
> Reporter: Gus Heck
> Priority: Minor
> Attachments: SOLR-12394.patch
>
>
> NodeConfig has a property called managementPath config which doesn't appear
> to serve any coherent function and is in fact documented in
> [https://lucene.apache.org/solr/guide/7_3/format-of-solr-xml.html] as:
> {quote}{{managementPath}}
> Currently non-operational.
> {quote}
> The code appears to have been added initially in SOLR-695, and that ticket
> appears to relate to an elimination of a special case for single core
> configurations. It seems that this may have been an attempt to support single
> cores that had no name (a legacy mode of operation I guess, but before my
> time) and yet still allow such single core setups to later have additional
> cores added?
> So this ticket is a suggestion that we remove this configuration that
> allegedly isn't working anyway, OR we make it work and give it good clear
> documentation in code and in the ref guide so that folks don't have to waste
> a lot of time figuring out what it does(n't do) to understand the code.
> Attaching patch to remove it.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
