[
https://issues.apache.org/jira/browse/SOLR-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708914#action_12708914
]
Markus commented on SOLR-1063:
------------------------------
Yonik,
I've launched Jetty in the example directory of Solr 1.3 but had, of
course, to modify the solrconf.xml to enable the
PHPSerializedResponseWriter by uncommenting that line. The following URL
will result in a unserializable string:
http://localhost:8983/solr/spellCheckCompRH/?q=*:*&spellcheck=true&spellcheck.q=tefst&spellcheck.collate=true&spellcheck.build=true&wt=phps
a:4:{s:14:"responseHeader";a:2:{s:6:"status";i:0;s:5:"QTime";i:5;}s:7:"command";s:5:"build";s:8:"response";a:3:{s:8:"numFound";i:0;s:5:"start";i:0;s:4:"docs";a:0:{}}s:10:"spellcheck";a:1:{s:11:"suggestions";a:0:{}}}
The next URL will fail to produce the proper result:
http://localhost:8983/solr/spellCheckCompRH/?q=*:*&spellcheck=true&spellcheck.extendedResults=true&spellcheck.q=tefst&spellcheck.collate=true&spellcheck.build=true&wt=phps
a:4:{s:14:"responseHeader";a:2:{s:6:"status";i:0;s:5:"QTime";i:5;}s:7:"command";s:5:"build";s:8:"response";a:3:{s:8:"numFound";i:0;s:5:"start";i:0;s:4:"docs";a:0:{}}s:10:"spellcheck";a:1:{s:11:"suggestions";a:1:{s:16:"correctlySpelled";true}}}
You can clearly see the extendedResults to be enabled in the latter URL.
Hope this helps, if not, then please let me know.
Good luck,
> Spellchecker result through wt=phps and wt=php
> ----------------------------------------------
>
> Key: SOLR-1063
> URL: https://issues.apache.org/jira/browse/SOLR-1063
> Project: Solr
> Issue Type: Bug
> Components: spellchecker
> Affects Versions: 1.3
> Environment: Debian Etch with Tomcat6 and Solr1.3
> Reporter: Markus
> Fix For: 1.4
>
>
> First of all, this is not through the provided PHP client but these are the
> actual results directly from Solr therefore the selected component is not
> Client/PHP but spellchecker. However, results like these are likely to be
> caused by the selected responsewriter since similar issues have been seen.
> There seems to be a bug in the PHPS outputHandler when retrieving a
> query that also produces spellcheck results.
> The following query fails to return an unserializable string:
> spellcheck=true&facet=true&indent=on&facet.mincount=1&spellcheck.extendedResults=true&
> spellcheck.q=groninen&spellcheck.collate=true&wt=phps&rows=8&start=0&
> q=generic_search:groninen&spellcheck.dictionary=jarowinkler&
> facet.field=city&facet.field=kitchen&facet.field=budget
> The problem is clearly visible at the end of the returned string:
> rectlySpelled";falses:9:"collation";s:9:"groningen";}}}
> The query works fine when extendedResults=false, otherwise this problem
> occurs.
> Using the PHP outputHandler instead also produces a result which i
> cannot pass through eval. It complains about the last line of the result
> which omits the semi colon.
> 'word'=>'groningen')),
> 'correctlySpelled'=>false,
> 'collation'=>'groningen')))
> It would also need a return statement to begin with in order to produce
> any results with eval. For a - simple - query to work properly you would
> need :
> $data = file_get_contents(query);
> var_dump(eval("return $data;"));
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
