[
https://issues.apache.org/jira/browse/SOLR-10826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Owen updated SOLR-10826:
----------------------------
Attachment: SOLR-10826.patch
OK I've expanded the test a bit, it now creates a second collection, and alias
for it, and a combined alias spanning both. Then it tests the various
combinations of {{collection=...}} values work as expected. Again, these tests
do fail without the code fix.
> 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
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
