[ 
https://issues.apache.org/jira/browse/SOLR-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Rowe updated SOLR-3251:
-----------------------------

    Attachment: SOLR-3251.patch

This patch builds on Yonik's patch:
* Persistence is added, both locally and to ZooKeeper.
* ZooKeeper persistence uses optimistic concurrency: when attempting to persist 
after adding a new field, if the remote version is different from the locally 
cached version, the schema is fetched from ZooKeeper, field definitions are 
reloaded (not the whole schema), and the field addition is redone and 
persistence is re-attempted, repeating until it succeeds.
* JSON PUT is enabled on /schema/fields/(name), in idempotent fashion: repeated 
identical requests don't result in schema changes (though no special check is 
done to achieve this - after such a request, the schema is still persisted as 
though there were a real change.)

So far there are only standalone tests, which pass.  I'm working on REST API 
tests and SolrCloud tests.

I'm not sure about whether anything needs to be done to enable replication of 
the managed schema, since it has a different name.  I think master/slave mode 
will just work, since AFAIK replication of config files triggers a core reload 
on the slaves.

I'd appreciate feedback on this, I think it's close.
                
> 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, 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]

Reply via email to