[
https://issues.apache.org/jira/browse/SOLR-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-7729:
------------------------------
Attachment: SOLR-7729.patch
Here is a patch that updates this to trunk.
This is all kind of awkward because the user can easily already have the
collection in the base url the client uses, but what can you do. This at least
fixes the bug.
> ConcurrentUpdateSolrClient ignoring the collection parameter in some methods
> ----------------------------------------------------------------------------
>
> Key: SOLR-7729
> URL: https://issues.apache.org/jira/browse/SOLR-7729
> Project: Solr
> Issue Type: Bug
> Components: SolrJ
> Affects Versions: 5.1
> Reporter: Jorge Luis Betancourt Gonzalez
> Assignee: Mark Miller
> Labels: client, solrj
> Attachments: SOLR-7729-ConcurrentUpdateSolrClient-collection.patch,
> SOLR-7729.patch
>
>
> Some of the methods in {{ConcurrentUpdateSolrClient}} accept an aditional
> {{collection}} parameter, some of this methods are: {{add(String collection,
> SolrInputDocument doc)}} and {{request(SolrRequest, String collection)}}.
> This collection parameter is being ignored in this cases but works for others
> like {{commit(String collection)}}.
> [~elyograg] noted that:
> {quote}
> Looking into how an update request actually gets added to the background
> queue in ConcurrentUpdateSolrClient, it appears that the "collection"
> information is ignored before the request is added to the queue.
> {quote}
> From the source, when a commit is issued or the
> {{UpdateParams.WAIT_SEARCHER}} is set in the request params the collection
> parameter is used, otherwise the request {{UpdateRequest req}} is queued
> without any regarding of the collection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
