Tomás Fernández Löbbe commented on SOLR-11960:

bq. The test failure described at SOLR-12061 started happening at the 
c1a44251fe commit on this issue.
Thanks Steve, I'll take a look
bq. It looks like there is no consumer to this API (yet) but watchers are being 
created anyway? We should avoid that until we have an actual user for this API.
I think you are right, there is no need to register the watch on 
{{registerCore}}. Users of this feature can add a watch themselves by calling 
{{registerCollectionPropsWatcher}}. That's what you mean, right?

> Add collection level properties
> -------------------------------
>                 Key: SOLR-11960
>                 URL: https://issues.apache.org/jira/browse/SOLR-11960
>             Project: Solr
>          Issue Type: New Feature
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Peter Rusko
>            Assignee: Tomás Fernández Löbbe
>            Priority: Major
>         Attachments: SOLR-11960.patch, SOLR-11960.patch, SOLR-11960.patch, 
> SOLR-11960.patch, SOLR-11960.patch
> Solr has cluster properties, but no easy and extendable way of defining 
> properties that affect a single collection. Collection properties could be 
> stored in a single zookeeper node per collection, making it possible to 
> trigger zookeeper watchers for only those Solr nodes that have cores of that 
> collection.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to