[
https://issues.apache.org/jira/browse/SOLR-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572774#comment-13572774
]
Steve Rowe commented on SOLR-3251:
----------------------------------
{quote}
bq. And the serialized representation in Zookeeper won't be a relational DB
(dump), but I suppose it could be JSON or YAML instead of XML
True, and it could also be broken down into individual keys rather than one big
"schema" blob... such that an individual field is defined under a schema tree
rather than a config "file" being stored in XML format.
{quote}
I was thinking that Zookeeper watches would be the way to broadcast changes.
Each znode (aka individual key) is distinguished from others by its fully
qualified name, so a field's "key" would have to be its "name" attribute. ZK
watches can be on znodes that don't exist yet, but it wouldn't be feasible to
set watches on the entire space of possible field names. So the watch would
have to be on the *parent* of the znodes for the individual fields.
Seems like batching schema changes would be useful, both on the sending and
receiving end. But having individual znodes for each field wouldn't allow for
batching notifications via watches - each change would trigger a watch.
> 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
