You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Varun Thacker (JIRA)" <ji...@apache.org> on 2017/07/06 20:33:00 UTC
[jira] [Updated] (SOLR-10826) CloudSolrClient using unsplit
collection list when expanding aliases
[ https://issues.apache.org/jira/browse/SOLR-10826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Varun Thacker updated SOLR-10826:
---------------------------------
Fix Version/s: 7.0
> CloudSolrClient using unsplit collection list when expanding aliases
> --------------------------------------------------------------------
>
> Key: SOLR-10826
> URL: https://issues.apache.org/jira/browse/SOLR-10826
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrJ
> Affects Versions: 6.4, 6.5.1, 6.6
> Reporter: Tim Owen
> Assignee: Varun Thacker
> Fix For: 7.0
>
> Attachments: SOLR-10826.patch, SOLR-10826.patch, SOLR-10826.patch
>
>
> Some recent refactoring seems to have introduced a bug in SolrJ's CloudSolrClient, when it's expanding a collection list and resolving aliases, it's using the wrong local variable for the alias lookup. This leads to an exception because the value is not an alias.
> E.g. suppose you made a request with {{&collection=x,y}} where either or both of {{x}} and {{y}} are not real collection names but valid aliases. This will fail, incorrectly, because the lookup is using {{x,y}} as a potential alias name lookup.
> Patch to fix this attached, which was tested locally and fixed the issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org