[
https://issues.apache.org/jira/browse/SOLR-4196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated SOLR-4196:
---------------------------------
Attachment: SOLR-4196.patch
Latest version. This has enough of the methods for the properties case to allow
at least a very simple test with using a properties file rather than a solr.xml
file to work. Nowhere near complete testing of using the properties file, a
start though.
I did violence to CoreDescriptor, having individual setters and getters when we
move to properties-based files seems unnecessary, so I combined the individual
fields into a Properties member var. I could be talked out of that, but it
seems like it's going in the right direction.
I think at this point we can see what this whole clumsy intermediate form for
back-compat will look like, gives me more sympathy for folks maintaining the
back-compat layers in Lucene <G>...
I was wondering if there's a way to wire in randomly using the properties case
or the xml-based case to leverage all of the tests built up over the years and
all the assumptions they make... haven't looked at how to do that at all
though....
> 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.1, 5.0
>
> Attachments: SOLR-4196.patch, SOLR-4196.patch, SOLR-4196.patch,
> SOLR-4196.patch
>
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
