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

Hoss Man commented on SOLR-13131:
---------------------------------

[~gus_heck] - i really appreciate you adding aliases.adoc as part of this 
issue, but it currently triggers several asciidoc warnings due to the use of 
{{1.}} multiple times in an ordered list (this is supported to make it easier 
for migrating docs from other markup syntaxes, but not recomended - hence the 
warnigs: https://asciidoctor.org/docs/user-manual/#ordered-lists ) ...
{noformat}
     [exec] asciidoctor: WARNING: aliases.adoc: line 26: list item index: 
expected 2, got 1
     [exec] asciidoctor: WARNING: aliases.adoc: line 27: list item index: 
expected 3, got 1
     [exec] asciidoctor: WARNING: aliases.adoc: line 225: list item index: 
expected 2, got 1
     [exec] asciidoctor: WARNING: aliases.adoc: line 226: list item index: 
expected 3, got 1
{noformat}

..could you please update these to use the recommended {{. }} syntax instead?

> Category Routed Aliases
> -----------------------
>
>                 Key: SOLR-13131
>                 URL: https://issues.apache.org/jira/browse/SOLR-13131
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>    Affects Versions: master (9.0)
>            Reporter: Gus Heck
>            Assignee: Gus Heck
>            Priority: Major
>             Fix For: 8.1, master (9.0)
>
>         Attachments: indexingWithCRA.png, indexingwithoutCRA.png, 
> indexintWithoutCRA2.png
>
>
> This ticket is to add a second type of routed alias in addition to the 
> current time routed aliases. The new type of alias will allow data driven 
> creation of collections based on the values of a field and automated 
> organization of these collections under an alias that allows the collections 
> to also be searched as a whole.
> The use case in mind at present is an IOT device type segregation, but I 
> could also see this leading to the ability to direct updates to tenant 
> specific hardware (in cooperation with autoscaling). 
> This ticket also looks forward to (but does not include) the creation of a 
> Dimensionally Routed Alias which would allow organizing time routed data also 
> segregated by device
> Further design details to be added in comments.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to