[ 
https://issues.apache.org/jira/browse/SOLR-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242248#comment-13242248
 ] 

Jan Høydahl commented on SOLR-1052:
-----------------------------------

The TRUNK patch is coming up, with these highlights:
* For luceneMatchVersion <= LUCENE_36 we parse <indexDefaults> and <mainIndex> 
and print warning
  This allows people to do drop-in upgrade keeping their old configs
* For luceneMatchVersion >= LUCENE_40 we FAIL fast if we find <indexDefaults> 
or <mainIndex>
* Converted all tests relying on solrconfig-*.xml files to new <indexConfig> 
format
* Removed a lot of redundant old <indexDefaults> and <mainIndex> config from 
test files

Questions:
* All tests which purpose is not to test the indexConfig stuff now uses 100% 
default settings
* This means among other things that lockType=native and unlockOnStartup=false. 
Are there known issues with such settings during tests?
                
> Deprecate/Remove <indexDefaults> and <mainIndex> in favor of <indexConfig> in 
> solrconfig.xml
> --------------------------------------------------------------------------------------------
>
>                 Key: SOLR-1052
>                 URL: https://issues.apache.org/jira/browse/SOLR-1052
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Grant Ingersoll
>            Assignee: Jan Høydahl
>              Labels: solrconfig.xml
>             Fix For: 3.6, 4.0
>
>         Attachments: SOLR-1052-3x-fix-tests.patch, SOLR-1052-3x.patch, 
> SOLR-1052-3x.patch, SOLR-1052-3x.patch, SOLR-1052-3x.patch
>
>
> Given that we now handle multiple cores via the solr.xml and the discussion 
> around <indexDefaults> and <mainIndex> at 
> http://www.lucidimagination.com/search/p:solr?q=mainIndex+vs.+indexDefaults
> We should deprecate old <indexDefaults> and <mainIndex> sections and only use 
> a new <indexConfig> section.
> 3.6: Deprecation warning if old section used
> 4.0: If LuceneMatchVersion before LUCENE_40 then warn (so old configs will 
> work), else fail fast

--
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to