lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donovan Jimenez (JIRA)" <>
Subject [jira] Commented: (SOLR-1091) "phps" (serialized PHP) writer produces invalid output
Date Wed, 06 May 2009 15:33:30 GMT


Donovan Jimenez commented on SOLR-1091:

the character sequence specified seems to be windows 1251 - based on just getting it to look
like what's in the description in a text editor. 

I see it getting the utf-8 byte length now, but is the output writer guaranteed to be outputting
in utf-8? sorry if it's a naive question, I do see the content-type is text/plain; charset=utf-8
- does that change the output writer's encoding?

if it IS guaranteed, then maybe its how the character data is added - i.e. the add xml was
interpreted utf-8 but the data was actually windows-1251 or similar.

> "phps" (serialized PHP) writer produces invalid output
> ------------------------------------------------------
>                 Key: SOLR-1091
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 1.3
>         Environment: Sun JRE 1.6.0 on Centos 5
>            Reporter: frank farmer
>            Priority: Minor
>             Fix For: 1.4
> The serialized PHP output writer can outputs invalid string lengths for certain (unusual)
input values.  Specifically, I had a document containing the following 6 byte character sequence:
> I was able to create a document in the index containing this value without issue; however,
when fetching the document back out using the serialized PHP writer, it returns a string like
the following:
> s:4:"􀁸";
> Note that the string length specified is 4, while the string is actually 6 bytes long.
> When using PHP's native serialize() function, it correctly sets the length to 6:
> # php -r 'var_dump(serialize("\xED\xAF\x80\xED\xB1\xB8"));'
> string(13) "s:6:"􀁸";"
> The "wt=php" writer, which produces output to be parsed with eval(), doesn't have any
trouble with this string.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message