[
https://issues.apache.org/jira/browse/SOLR-13122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874073#comment-16874073
]
Gus Heck edited comment on SOLR-13122 at 6/27/19 12:27 PM:
-----------------------------------------------------------
I actually don't much like the collection drop down on the left. If anything
goes it should be that. It's terribly hard to use if you have >10 collections
or collection names longer than "foobar" Make one Time Routed Alias with daily
collections for a month (which soon creates 30 collections named
tweetsOrSomething_2019-06-XX) and then try to find your other collection
"foobar" among the 30 wrapping entries in that drop down ... yeah you have
type ahead, but the drop down part becomes entirely useless. If you don't
know/can't remember the collection name (or are exploring a new client's
install on a testing machine?) the drop down is a pretty bad view of what
exists. (and you would never even find the aliases without a lot of looking).
One convenience for testing what things look like with lots of collections
would be to create a TRA with a start date in the past and set maxFutureMs to
something very high, and then send in one doc (via documents) with an id and
the current date... it will then create a bunch of longish collection names for
you. Note that I once did this with monthly collections since 1970 (a client
was trying and luckily failing to do that, I did it just for fun locally to see
if it could even work) and it crushed the system and died after the 500th
collection and like 20 minutes so don't get too carried away :).
was (Author: gus_heck):
I actually don't much like the collection drop down on the left. If anything
goes it should be that. It's terribly hard to use if you have >10 collections
or collection names longer than "foobar" Make one Time Routed Alias with daily
collections for a month (which soon creates 30 collections named
tweetsOrSomething_2019-06-XX) and then try to find you other collection
"foobar" among the 30 wrapping entries in that drop down ... yeah you have
type ahead, but the drop down part becomes entirely useless. If you don't
know/can't remember the collection name (or are exploring a new client's
install on a testing machine?) the drop down is a pretty bad view of what
exists. (and you would never even find the aliases without a lot of looking).
One convenience for testing what things look like with lots of collections
would be to create a TRA with a start date in the past and set maxFutureMs to
something very high, and then send in one doc (via documents) with an id and
the current date... it will then create a bunch of longish collection names for
you. Note that I once did this with monthly collections since 1970 (a client
was trying and luckily failing to do that, I did it just for fun locally to see
if it could even work) and it crushed the system and died after the 500th
collection and like 20 minutes so don't get too carried away :).
> 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
> Fix For: 8.2
>
> Attachments: alias-collection-menu-selected.png,
> alias-collection-view.png, alias-collections-menu.png,
> alias-collections-menu.png, alias-delete-dialogue.png, alias-dropdown.png,
> alias-select-double.png, alias-view.png, new-collection-dropdown.png,
> new-oll-overview.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
