On Mon, Aug 27, 2012 at 10:23 AM, Vladimir Shapovalov
wrote:
> Thank you for the explanation.
>
> It looks like the serialization routine in one case (solr) encodes
> characters_to_binary()
> and by normal fetch not. Assuming we fetch in JSON in both cases.
>
No, Olav is incorrect in his analysi
Thank you for the explanation.
It looks like the serialization routine in one case (solr) encodes
characters_to_binary()
and by normal fetch not. Assuming we fetch in JSON in both cases.
I'm requesting same data in same format, i.e. JSON.
Once by fetching object like /buckets/bucket/keys/key.
And
Hey Olaf,
Thanks for the answer.
Yep, I know, it's JSON compliant.
The question is, why the unicode escaped sequences appear only in case of
searching and retrieveing in JSON? This is not the case in XML output.
If I just get the same key directly in JSON, the unicode chars are NOT
escaped.
Che
Hi all,
I've a key in a bucket, witch is indexed.
{
...
"street":"Sabinastraße"
...
}
If I retrieve the key this way:
curl -i -v http://localhost:8098/buckets/is_solr/keys/123
The response looks like:
{
...
"street":"Sabinastraße"
...
}
which is correct.
If I search for key and expect XML out
