You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Gus Heck (Jira)" <ji...@apache.org> on 2021/06/17 16:27:00 UTC
[jira] [Commented] (SOLR-13375) 2 Dimensional Routed Aliases
[ https://issues.apache.org/jira/browse/SOLR-13375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17365008#comment-17365008 ]
Gus Heck commented on SOLR-13375:
---------------------------------
Just saw this question, If you are talking about:
{code:java}
public void shutdown() {
+
+ ZkController zkController = getZkController();
+ if (zkController != null) {
+ OverseerTaskQueue overseerCollectionQueue = zkController.getOverseerCollectionQueue();
+ overseerCollectionQueue.allowOverseerPendingTasksToComplete();
+ }
log.info("Shutting down CoreContainer instance=" + System.identityHashCode(this));
{code}
Yes I believe that is the point. See the later part of my comment on this issue dated July 5 2019
> 2 Dimensional Routed Aliases
> ----------------------------
>
> Key: SOLR-13375
> URL: https://issues.apache.org/jira/browse/SOLR-13375
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Affects Versions: main (9.0)
> Reporter: Gus Heck
> Assignee: Gus Heck
> Priority: Major
> Attachments: SOLR-13375.patch, SOLR-13375.patch, SOLR-13375.patch, SOLR-13375.patch, SOLR-13375.patch
>
>
> Current available routed aliases are restricted to a single field. This feature will allow Solr to provide data driven collection access, creation and management based on multiple fields in a document. The collections will be queried and updated in a unified manner via an alias. Current routing is restricted to the values of a single field. The particularly useful combination at this time will be Category X Time routing but Category X Category may also be useful. More importantly, if additional routing schemes are created in the future (either as contributions or as custom code by users) combination among these should be supported.
> It is expected that not all combinations will be useful, and that determination of usefulness I expect to leave up to the user. Some Routing schemes may need to be limited to be the leaf/last routing scheme for technical reasons, though I'm not entirely convinced of that yet. If so, a flag will be added to the RoutedAlias interface.
> Initial desire is to support two levels, though if arbitrary levels can be supported easily that will be done.
> This could also have been called CompositeRoutedAlias, but that creates a TLA clash with CategoryRoutedAlias.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org