[ 
https://issues.apache.org/jira/browse/SOLR-11960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371487#comment-16371487
 ] 

Gus Heck commented on SOLR-11960:
---------------------------------

Interesting notion. As far as what we did with time routed aliases, I think 
it's probably less confusing the way we did it to have alias level 
metadata/props, since the time routing is at the alias level, and collections 
come and go over time. The ability to keep metadata at multiple levels of 
abstraction is good, what might be interesting is a way to combine and keep 
metadata all in one api. One could identify the targets (subjects) via URIs 
that correspond to the API such as 
http://server.example.net:8983/solr/meta/aliases/aliasname 
http://server.example.net:8983/solr/meta/nodes/nodename 
http://server.example.net:8983/solr/meta/collections/collectionName/shards/shardname....
 etc. basically make the entire system addressable. Also maybe coordinate that 
with the v2 api?  Just brainstorming, I haven't figured out how that would 
relate to zookeeper. A unified and consistent way of handling metadata sounds 
potentially helpful now that we are gaining a 3rd metadata type. Might be 
possible to give metadata addressable java objects a metaURI() method that 
automatically provides the key for that object in a global metadata store...

> 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 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

Reply via email to