[
https://issues.apache.org/jira/browse/SOLR-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623770#comment-13623770
]
Yonik Seeley commented on SOLR-3251:
------------------------------------
bq. But your same hypothetical issue can happen inside e.g. codec code if
suddenly the codec returns different things: its exactly the same problem and
would be 'hard to enumerate and ongoing' just like it would be for solr search
code!
Right, but I'm hoping that the scope of potential problems in lucene indexing
code is much more limited than all of the solr search code.
The Codec in SchemaCodecFactory only overrides getPostingsFormatForField and
getDocValuesFormatForField. It depends on how those objects are used in Lucene
(if those methods are called more than once for the same field or not). Then
we need to understand what postings format changes and docvalue format changes
are OK (if any).
At the very least, there are a number of changes at the Solr level that will
not change anything at the Lucene level (like changing multiValued from false
to true for instance).
> dynamically add field to schema
> -------------------------------
>
> Key: SOLR-3251
> URL: https://issues.apache.org/jira/browse/SOLR-3251
> Project: Solr
> Issue Type: New Feature
> Reporter: Yonik Seeley
> Assignee: Steve Rowe
> Attachments: SOLR-3251.patch, SOLR-3251.patch, SOLR-3251.patch
>
>
> One related piece of functionality needed for SOLR-3250 is the ability to
> dynamically add a field to the schema.
--
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
