[
https://issues.apache.org/jira/browse/SOLR-11960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394237#comment-16394237
]
David Smiley commented on SOLR-11960:
-------------------------------------
Copying an excerpt of my comment from SOLR-11617:
bq. The paint is still wet on SOLR-11960, so to speak. Before it's API gets set
in stone (by a 7.3 release), perhaps now is the last moment to give the API
more of a bulk parameter feel (like here for aliases) instead of limited to one
at a time? Even if the code can only handle one pair right now, at least the
API would be what we want it to be.
You can see how this is done with alias metadata (soon to be renamed
properties). Lets make such a change ASAP; ehh?
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
