You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2013/06/03 20:35:20 UTC
[jira] [Commented] (SOLR-4715) CloudSolrServer does not provide
support for setting underlying server properties
[ https://issues.apache.org/jira/browse/SOLR-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673412#comment-13673412 ]
Shawn Heisey commented on SOLR-4715:
------------------------------------
I appear to have done something really wrong. I'll have a new patch up soon. The following applies to the latest patch, but I think that it also applies to the one that's already attached:
The first part of LBHttpSolrServerTest#testLBHttpSolrServerHttpClientResponseParserStringArray fails with my patch, because when a null value is passed in, the object will create the parser/writer rather than assign the null. Is there ever a valid reason to have a null parser?
A lot of other solrj tests fail, mostly due to parsing errors in XMLResponseParser, but also due sometimes to NullPointerException.
The patch also appears to be responsible for a failure in the core test named TestCloudManagedSchema:
{noformat}
[junit4:junit4] > Throwable #1: java.lang.RuntimeException: java.io.UnsupportedEncodingException: text/plain; charset=ISO-8859-1
[junit4:junit4] > at __randomizedtesting.SeedInfo.seed([6B54507467721A2F:EAB2DE6C102D7A13]:0)
[junit4:junit4] > at org.apache.solr.schema.TestCloudManagedSchema$RawResponseParser.processResponse(TestCloudManagedSchema.java:104)
[junit4:junit4] > at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:440)
[junit4:junit4] > at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:213)
[junit4:junit4] > at org.apache.solr.schema.TestCloudManagedSchema.getFileContentFromZooKeeper(TestCloudManagedSchema.java:87)
[junit4:junit4] > at org.apache.solr.schema.TestCloudManagedSchema.doTest(TestCloudManagedSchema.java:67)
[junit4:junit4] > at org.apache.solr.BaseDistributedSearchTestCase.testDistribSearch(BaseDistributedSearchTestCase.java:815)
[junit4:junit4] > at java.lang.Thread.run(Thread.java:722)
[junit4:junit4] > Caused by: java.io.UnsupportedEncodingException: text/plain; charset=ISO-8859-1
[junit4:junit4] > at sun.nio.cs.StreamDecoder.forInputStreamReader(StreamDecoder.java:71)
[junit4:junit4] > at java.io.InputStreamReader.<init>(InputStreamReader.java:100)
[junit4:junit4] > at org.apache.commons.io.IOUtils.copy(IOUtils.java:1435)
[junit4:junit4] > at org.apache.commons.io.IOUtils.toString(IOUtils.java:585)
[junit4:junit4] > at org.apache.solr.schema.TestCloudManagedSchema$RawResponseParser.processResponse(TestCloudManagedSchema.java:102)
[junit4:junit4] > ... 45 more
{noformat}
> CloudSolrServer does not provide support for setting underlying server properties
> ---------------------------------------------------------------------------------
>
> Key: SOLR-4715
> URL: https://issues.apache.org/jira/browse/SOLR-4715
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.3
> Reporter: Hardik Upadhyay
> Assignee: Shawn Heisey
> Labels: solr, solrj
> Attachments: SOLR-4715-incomplete.patch
>
>
> CloudSolrServer (and LBHttpSolrServer) do not allow the user to set underlying HttpSolrServer and HttpClient settings without arcane java enchantments.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org