[
https://issues.apache.org/jira/browse/SOLR-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614814#action_12614814
]
Noble Paul commented on SOLR-619:
---------------------------------
If the fields are made volatile , should it be ok? How expensive are volatile
fields?
bq.I think adding copyFields should (for now) be restricted to use before or
during the inform() phase.
I would g w/ this approach.Making reads expensive is *not an option*.
> Register copyField at runtime
> -----------------------------
>
> Key: SOLR-619
> URL: https://issues.apache.org/jira/browse/SOLR-619
> Project: Solr
> Issue Type: New Feature
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Priority: Minor
> Fix For: 1.3
>
> Attachments: SOLR-619-RuntimeSchema.patch, SOLR-619.patch
>
>
> In order to enable runtime schema manipulation, it would be nice to register
> copy fields manually rather then requiring them to be registered via
> schema.xml.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
