[
https://issues.apache.org/jira/browse/SOLR-4196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reopened SOLR-4196:
-------------------------------
I think there are some issues to look at here - there are a variety of non
thread safe accesses to shared variables. That's not really a valid way to
avoid deadlocks.
> Untangle XML-specific nature of Config and Container classes
> ------------------------------------------------------------
>
> Key: SOLR-4196
> URL: https://issues.apache.org/jira/browse/SOLR-4196
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Minor
> Fix For: 4.3, 5.0
>
> Attachments: SOLR-4196.patch, SOLR-4196.patch, SOLR-4196.patch,
> SOLR-4196.patch, SOLR-4196.patch, SOLR-4196.patch, SOLR-4196.patch,
> SOLR-4196.patch, SOLR-4196.patch, SOLR-4196.patch, SOLR-4196.patch,
> SOLR-4196.patch, SOLR-4196.patch, SOLR-4196.patch, StressTest.zip,
> StressTest.zip, StressTest.zip, StressTest.zip
>
>
> sub-task for SOLR-4083. If we're going to try to obsolete solr.xml, we need
> to pull all of the specific XML processing out of Config and Container.
> Currently, we refer to xpaths all over the place. This JIRA is about
> providing a thunking layer to isolate the XML-esque nature of solr.xml and
> allow a simple properties file to be used instead which will lead,
> eventually, to solr.xml going away.
--
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: [email protected]
For additional commands, e-mail: [email protected]
