[
https://issues.apache.org/jira/browse/SOLR-11960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16375698#comment-16375698
]
Gus Heck commented on SOLR-11960:
---------------------------------
{quote} Since aliases operate in the same namespace as collections, I don't
think of it as separate.
{quote}
Interesting point, and kinda points out the fact that "alias" has been co-opted
into 2 roles, alternate names for collections and collection grouping. This
creates a level of syntactic sugar (query a group just like a single
collection) but grouping and re-naming really are separate concepts. To handle
alternate names for groups of collections you would need recursive alias
resolution.
> 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
