Just ran into the same issue with 0.19.1.
I've upgraded a server from 0.18.7. Client uses the Java API with transport
connection. Getting sourceAsString from the hit now returns a malformed
string (containing all kind of junk bytes).
Some more things that may help -
If I look at the toString of the response object itself the sources look
fine, opposed to getting it from the hit with sourceAsString.
When searching I get some errors from some indices (which is fine - the
errors themselves are something that I expect). But the formatting of the
query on the server side seems again wrong, as if the index didn't read the
Parse Failure [Failed to parse source
Parse Failure [No mapping found for [pt.$date] in order to sort on]];
This of course blocks from upgrading to the new release...
On Wednesday, March 14, 2012 2:15:14 PM UTC+2, kimchy wrote:
Can you provide a simple Java recreation for this? If its a problem,
would love to fix this for 0.19.1.
On Tuesday, March 13, 2012 at 4:58 PM, Jan Fiedler wrote:
I ran into a strange regression in a test case when upgrading to 0.19.0.
The test uses the Java API (and I therefore do not have a standalone curl
regression at hand). The test is creating a brand new index every time so
the issue can not be related to data indexed with 0.18.x. Before digging
deeper I wanted to check if anybody has seen similar issues. This is the
exception I am seeing when trying to get call 'sourceAsString' on a search