[jira] [Updated] (SOLR-8738) invalid DBQ initially sent to a non-leader node will report success

2016-04-21 Thread Anshum Gupta (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-8738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshum Gupta updated SOLR-8738: --- Fix Version/s: 5.5.1 6.0 > invalid DBQ initially sent to a non-leader node will

[jira] [Updated] (SOLR-8738) invalid DBQ initially sent to a non-leader node will report success

2016-02-29 Thread Hoss Man (JIRA)
[ 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

[jira] [Updated] (SOLR-8738) invalid DBQ initially sent to a non-leader node will report success

2016-02-26 Thread Hoss Man (JIRA)
[ 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 The crux of why the errors are silently ignored seems to be because

[jira] [Updated] (SOLR-8738) invalid DBQ initially sent to a non-leader node will report success

2016-02-25 Thread Hoss Man (JIRA)
[ 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 here's a MiniSolrCloudCluster based test patch i hacked out of the existing