[
https://issues.apache.org/jira/browse/SOLR-13122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874210#comment-16874210
]
Erick Erickson commented on SOLR-13122:
---------------------------------------
[~janhoy] We're on the same page actually. You wrote:
"I’m ok with an alias with same name if it is 100% we’ll defined everywhere
that it is the alias that takes precedence..."
I don't have complete faith that we've done that. Or that even if we do
everyone will be aware of whatever rules we define and follow them in future.
And AFAICT, we don't have tests that test all of the conditions. I'm in favor
of requiring that aliases and collections be disjoint sets of names if we have
a path for users to deal with the situation I outlined. Currently, one little
programming error and it's a catastrophe. Say somebody deletes an alias and we
follow it and delete the underlying collection.....
Wait, wait, wait.... My concern was that users could realize later that they
needed to use aliases and couldn't/wouldn't be able to change their apps to use
an alias with a different name. But I forgot about the collections API RENAME
call that Andrzej put in, see SOLR-13262.
That changes things IMO. The risk I outlined about blowing away one collection
temporarily goes away. The process would look like:
1> RENAME C1 to C1_something
2> CREATEALIAS C1 -> C1_something
Now swap the alias to point to C2_something or C1_something at will. Or create
C2_something first and alias to that. or.. Doesn't matter, people have a way to
atomically switch and still have a fallback. I don't know the behavior when
queries come in between <1> and <2>, but IMO if requests are a little wonky for
a few minutes or if it requires a one-time maintenance window it's acceptable.
We're talking a very short window.
This sounds like another JIRA though. I also haven't used RENAME so this is a
little theoretical. And we could also create a really explicit error message
like "you cannot create an alias with the same name as an existing collection,
you must RENAME or DELETE the collection first"
> 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: [email protected]
For additional commands, e-mail: [email protected]
