You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Gus Heck (JIRA)" <ji...@apache.org> on 2019/07/13 22:39: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=16884509#comment-16884509 ]
Gus Heck commented on SOLR-13375:
---------------------------------
Patch with docs & cleanup ready for commit in a day or two unless I hear objections. Support only for 2D Dimensional Routed Aliases since there are folks waiting with the 2D use case in mind and I need to attend to other work before I sort out the 3+ dimension cases. This patch flat out forbids more than 2 dimensions so nobody tries to use what's not yet working. The V1 and V2 API's already fully support the creation of N dimensions, but the collection creation isn't quite behaving itself in the 3 category case I tested while writing docs so the collections API portion of this is not going to change other than eventually it won't error out for more than 2 dims.
> 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: master (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
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org