1:"recommended";i:false;}
I think that PHP's unserialize function may be failing due to the wrong value
for the datatype.
> A PHP response writer for Solr
> --
>
> Key: SOLR-196
> URL: https://is
articular field?
Can you post the output from fl=recommended?
Is it particular values of that field that cause the problem, or *any* document
retrieved with that field? If particular values, perhaps you could narrow it
down and just post the problematic value?
> A PHP response wri
r fails
to unserialize in PHP5.
> A PHP response writer for Solr
> --
>
> Key: SOLR-196
> URL: https://issues.apache.org/jira/browse/SOLR-196
> Project: Solr
> Issue Type: New Feature
>
from the php response writer fails to
unserialize in PHP5.
> A PHP response writer for Solr
> --
>
> Key: SOLR-196
> URL: https://issues.apache.org/jira/browse/SOLR-196
> Project: Solr
>
This PHP writer is inconsistent with the JSON if you use php 5's decode_json,
maps come back as objects.
was (Author: pwolanin):
This serialized writer produces output that is inconsistent with the other
PHP writer and inconsistent with the JSON.
> A PHP response wri
This serialized writer produces output that is inconsistent with the other PHP
writer and inconsistent with the JSON.
was (Author: pwolanin):
This serialized writer produces output that is inconsistent with the other
PHP writer adn inconsistent with the JSON
> A PHP response wri
t is inconsistent with the other PHP
writer adn inconsistent with the JSON
> A PHP response writer for Solr
> --
>
> Key: SOLR-196
> URL: https://issues.apache.org/jira/browse/SOLR-196
> Project: Solr
>
me :-)
-Yonik
> A PHP response writer for Solr
> --
>
> Key: SOLR-196
> URL: https://issues.apache.org/jira/browse/SOLR-196
> Project: Solr
> Issue Type: New Feature
> Component
added properly
during the latest commit:
/src/java/org/apache/solr/request/PHPResponseWriter.java
/src/java/org/apache/solr/request/PHPSerializedResponseWriter.java
We won't get very far without those!
> A PHP response writer for Solr
> --
>
>
goal so it's
probably better to leave the content-types unchanged for the moment.
> A PHP response writer for Solr
> --
>
> Key: SOLR-196
> URL: https://issues.apache.org/jira/browse/SOLR-196
> Pro
[
https://issues.apache.org/jira/browse/SOLR-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-196.
---
Resolution: Fixed
Thanks guys!
I just committed this.
> A PHP response writer for S
[
https://issues.apache.org/jira/browse/SOLR-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518054
]
Nick Jenkin commented on SOLR-196:
--
Excellent stuff, thanks Pieter!
> A PHP response writer for S
actually see
the result in a browser.
Is there a content-type we can use for JSON that can achieve both goals for
firefox and IE at least?
> A PHP response writer for Solr
> --
>
> Key: SOLR-196
> URL: https://issues.
by Paul Borgermans
and integrates the serialized PHP response writer (renamed to
PHPSerializedResponseWriter to avoid name clashes) originally authored by Nick
Jenkin in SOLR-275. See
http://www.nabble.com/PHP-Response-Writer-for-Solr-tf4140580.html for some
discussion on this implementation
On 8/2/07, Pieter Berkel <[EMAIL PROTECTED]> wrote:
> On 31/07/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> >
> > I'd be for refactors that wouldn't slow down the current JSON writer,
> > or increase it's memory footprint.
> >
> > As a specific example, if serializing something like Iterable, the
On 31/07/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
>
> I'd be for refactors that wouldn't slow down the current JSON writer,
> or increase it's memory footprint.
>
> As a specific example, if serializing something like Iterable, the
> JSON writer should still be able to stream each element rather
distribution.
>
> http://www.nabble.com/Created%3A-%28SOLR-196%29-A-PHP-response-writer-for-Solr-tf3458434.html
> http://www.nabble.com/-jira--Created%3A-%28SOLR-275%29-PHP-Serialized-Response-Writer-tf3980951.html
>
> There is quite a bit of code duplication in SOLR-196 which I'
I've been using the proposed PHP response writer code from SOLR-196
(eval-able php code) and SOLR-275 (serialized php data) for some time now
and would like to work towards getting these included in the main Solr
distribution.
http://www.nabble.com/Created%3A-%28SOLR-196%29-A-PHP-response-w
l are not too strong yet).
cheers,
Tristan
> A PHP response writer for Solr
> --
>
> Key: SOLR-196
> URL: https://issues.apache.org/jira/browse/SOLR-196
> Project: Solr
> Issue Type: New Fea
want to touch the
Python and Ruby response writers (yet).
My next priority however is to release a set of PHP classes to interact with
Solr. If these protected variables appear, the PHP response writer will be
immediately adapted.
Regards
Paul
> A PHP response writer for S
like
ARRAY_START, ARRAY_SEP, ARRAY_END, etc, would allow us to eliminate some code
duplication?
> A PHP response writer for Solr
> --
>
> Key: SOLR-196
> URL: https://issues.apache.org/jira/browse/SOLR-196
>
response writer (patch made
against trunk rev 516287)
This relies on a correct schema.xml config file with respect to multi valued
fields!! Otherwise, duplicate keys are generated.
> A PHP response writer for Solr
> --
>
> K
A PHP response writer for Solr
--
Key: SOLR-196
URL: https://issues.apache.org/jira/browse/SOLR-196
Project: Solr
Issue Type: New Feature
Components: clients - php, search
Reporter: Paul
23 matches
Mail list logo
