[
https://issues.apache.org/jira/browse/SOLR-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622903#comment-13622903
]
Robert Muir commented on SOLR-3251:
-----------------------------------
Well here's how i see it honestly (given the situation the schema is currently
mutable and if you gave me enough beers, i bet i could find piles of code in
the current tree that have subtle reliance upon that fact):
* option A: immutable
* option B: mutable, but we drink those beers and look for those pieces of code
and discuss and fix them.
I'm just having trouble seeing how option B can really work.
Typically in a case like this, you'd just add some "safeguards", e.g. shit like
clone()/freeze()/factor out abstract schema+unmodifiable()/whatever: then these
pieces of code can get immutable "snapshots" and go about their merry way.
but if you do this, then it really doesn't fix the problem, simply brings back
bugs like SOLR-4417 all over again: "you can add your new field to the schema,
and its instant, but just dont index any documents with it without doing a core
reload first, or all kinds of shit like similarity and codecs doesnt work"
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
