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

[~dsmiley] I think both would be nice. For v1 APIs, the single property at a 
time format is simpler and more verbose. The multiple at a time is more 
"expert" (in V2 it doesn't matter). Also, for collection properties we should 
add support for adding properties at collection creation time. So, I'd suggest 
we keep the current format and add the bulk one for collection and cluster 
properties as a separate Jira. Could be something like:
The same parameters could work for {{action=CLUSTERPROP}} and for 

Similarly, we could have

> 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: Blocker
>             Fix For: 7.3
>         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