-
Notifications
You must be signed in to change notification settings - Fork 24.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transform script and completion suggest payload - malformed JSON output #8959
Comments
Thanks for the reproduction steps. I'll have a look. |
Ok, figured it out. I'll have a pull request to fix it in a bit. |
very cool ;) |
When I originally wrote the transform feature I didn't think that the XContentType of the reencoded source mattered. It actually matters because payloads for the completion suggester are stored and returned exactly as encoded by this XContentType. This revision changes the transform feature from always reencoding with smile to always reencoding with the provided XContentType to support the completion suggester. Closes elastic#8959
@jo-m OK - fix in pull request sent. To actually get the fix applied you'd have to upgrade to a version of Elasticsearch with the fix merged (assuming it is merged) and reindex the documents. You might also want to look at #8975 which, if we go ahead and fix that too, would make reindexing the documents no longer required. |
thank you! |
thanks @nik9000! |
When I originally wrote the transform feature I didn't think that the XContentType of the reencoded source mattered. It actually matters because payloads for the completion suggester are stored and returned exactly as encoded by this XContentType. This revision changes the transform feature from always reencoding with smile to always reencoding with the provided XContentType to support the completion suggester. Closes #8959
When I originally wrote the transform feature I didn't think that the XContentType of the reencoded source mattered. It actually matters because payloads for the completion suggester are stored and returned exactly as encoded by this XContentType. This revision changes the transform feature from always reencoding with smile to always reencoding with the provided XContentType to support the completion suggester. Closes #8959
When I originally wrote the transform feature I didn't think that the XContentType of the reencoded source mattered. It actually matters because payloads for the completion suggester are stored and returned exactly as encoded by this XContentType. This revision changes the transform feature from always reencoding with smile to always reencoding with the provided XContentType to support the completion suggester. Closes #8959
When I originally wrote the transform feature I didn't think that the XContentType of the reencoded source mattered. It actually matters because payloads for the completion suggester are stored and returned exactly as encoded by this XContentType. This revision changes the transform feature from always reencoding with smile to always reencoding with the provided XContentType to support the completion suggester. Closes elastic#8959
When I originally wrote the transform feature I didn't think that the XContentType of the reencoded source mattered. It actually matters because payloads for the completion suggester are stored and returned exactly as encoded by this XContentType. This revision changes the transform feature from always reencoding with smile to always reencoding with the provided XContentType to support the completion suggester. Closes elastic#8959
I am using the completion suggester. The payload is being created using a transform script. This somehow breaks JSON output. A detailed shell script for reproducing the bug is included. This was tested with version 1.4.0.
This produces output like this:
The text was updated successfully, but these errors were encountered: