lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-8738) invalid DBQ initially sent to a non-leader node will report success
Date Tue, 01 Mar 2016 00:18:18 GMT

     [ https://issues.apache.org/jira/browse/SOLR-8738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hoss Man updated SOLR-8738:
---------------------------
    Attachment: SOLR-8738.patch

Updated patch to refactor test to take advantage of SolrCloudTestCase added by SOLR-8758.

Still need someone who actually understands this code to review the non-test changes.

> invalid DBQ initially sent to a non-leader node will report success
> -------------------------------------------------------------------
>
>                 Key: SOLR-8738
>                 URL: https://issues.apache.org/jira/browse/SOLR-8738
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>         Attachments: SOLR-8738.patch, SOLR-8738.patch, SOLR-8738.patch
>
>
> Discovered this while working on SOLR-445.
> If a Delete By Query gets sent to a node which is not hosting a leader (ie: only hosts
replicas, or doesn't host any cores related to the specified collection) then a success will
be returned, even if the DBQ is completely malformed and actually failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message