[
https://issues.apache.org/jira/browse/SOLR-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved SOLR-3610.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.0
4.0
Assignee: Robert Muir
I committed this. I think the indexwriter config is a larger issue, so turning
this off by default means a majority of people won't get bit by it.
> After reloading a core, indexing will fail on any newly added fields to the
> schema.
> -----------------------------------------------------------------------------------
>
> Key: SOLR-3610
> URL: https://issues.apache.org/jira/browse/SOLR-3610
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.0-ALPHA
> Reporter: Robert Muir
> Assignee: Robert Muir
> Fix For: 4.0, 5.0
>
> Attachments: SOLR-3610.patch, SOLR-3610.patch
>
>
> This is just another instantiation of SOLR-3587.
> Because the IndexWriter is kept open, the Codec still uses the old schema,
> and when asked to index for the field, doesn't know about it and returns an
> error.
> We could dodge the problem for now by turning off per-field codec support by
> default, requiring users to turn it on explicitly in solrconfig.xml (like
> similarity), knowing they are making a tradeoff by doing that (same goes for
> Similarity if you are using a per-field configuration).
--
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
