[
https://issues.apache.org/jira/browse/SOLR-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572851#comment-13572851
]
Steve Rowe commented on SOLR-3251:
----------------------------------
On schema serialization, I prefer not to keep a separate file for new fields,
because updated fields will need special handling, and deleted fields will need
either a separate file or an operation attribute (add or delete) in the
separate file. Just seems like the design will be simpler if we keep it to
just one file.
I'm guessing the intent with the separate file is that it would be simpler to
isolate changes and not have to reload the entire schema when a field is added.
I think the reload costs can be reduced by comparing each component
(field/fieldtype) to its previous serialized form, and only re-instantiating if
not identical. (This strategy would require some form of canonicalization to
work properly.)
> 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
> Attachments: 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
