You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2013/02/18 01:03:13 UTC
[jira] [Commented] (SOLR-3610) After reloading a core, indexing
will fail on any newly added fields to the schema.
[ https://issues.apache.org/jira/browse/SOLR-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580335#comment-13580335 ]
Mark Miller commented on SOLR-3610:
-----------------------------------
We should be able to fix this now that SOLR-4417 is in.
> 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-BETA, 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org