[
https://issues.apache.org/jira/browse/SOLR-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979715#action_12979715
]
Antonio Verni commented on SOLR-2307:
-------------------------------------
yes, exactly, and it could also fix SOLR-2278 but I didn't tested it.
As I discovered reading your SOLR-2291, the current patch I uploaded does not
respect returnFields parameter. I've fixed it but I need to upload a third
version of the patch (so please, sorry the mess) and a new test file.
In detail, to fix the issue I've added a numeric index to the "response" array
of documents in writeSolrDocumentList as requested by the php serialization
protocol and handled the field count in writeSolrDocument.
> PHPSerialized fails with sharded queries
> ----------------------------------------
>
> Key: SOLR-2307
> URL: https://issues.apache.org/jira/browse/SOLR-2307
> Project: Solr
> Issue Type: Bug
> Components: Response Writers
> Affects Versions: 1.3, 1.4.1
> Reporter: Antonio Verni
> Priority: Minor
> Attachments: PHPSerializedResponseWriter.java.patch,
> PHPSerializedResponseWriter.java.patch, TestPHPSerializedResponseWriter.java
>
>
> Solr throws a "java.lang.IllegalArgumentException: Map size must not be
> negative exception" when using the PHP Serialized response writer with
> sharded queries.
> To reproduce the issue start your preferred example and try the following
> query:
> http://localhost:8983/solr/select/?q=*:*&wt=phps&shards=localhost:8983/solr,localhost:8983/solr
> It is caused by the JSONWriter implementation of writeSolrDocumentList and
> writeSolrDocument. Overriding this two methods in the
> PHPSerializedResponseWriter to handle the SolrDocument size seems to solve
> the issue.
> Attached my patch made against trunk rev 1055588.
> cheers,
> Antonio
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
