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

Jan Høydahl commented on SOLR-13122:
------------------------------------

I plan to pick this up. Here's my plan
 # Query if there are any aliases, if so, list them *on top* of the collections 
dropdown, with a horizontal bar delimiting collections
 # When an alias is selected, only show the menu options "Query" and"Stream". 

Questions
 * Is it so now that every collection created now has an alias with the same 
name pointing to it? If so, perhaps skip these aliases in the list?
 * Would the schema endpoint work for aliases? Other endpoints that make sense 
to show for aliases?
 * Should we make any special treatment of an alias X that point to exactly one 
collection Y? Versus those that point to multiple collections? For clarity I 
think treating all aliases the same and not trying to be smart routing some 
requests to the alias and some to the underlying collection is the best choice.
 * Other input before I throw up the first patch?

> Ability to query aliases in Solr Admin UI
> -----------------------------------------
>
>                 Key: SOLR-13122
>                 URL: https://issues.apache.org/jira/browse/SOLR-13122
>             Project: Solr
>          Issue Type: Improvement
>          Components: Admin UI
>            Reporter: mosh
>            Assignee: Jan Høydahl
>            Priority: Major
>              Labels: UI
>
> After having recently toyed with Time Routed Alias in SolrCloud,
> we have noticed there is no way to query an alias from the admin UI,
> since the combo box only contains the current collection in the cluster.
> Solr Admin UI ought to have a way to query these aliases, for better 
> convenience.



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