-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
opensearchpy.exceptions.RequestError: Illegal character ((CTRL-CHAR, code 31)): only regular white space (\\r, \\n, \\t) is allowed between tokens #10747
Comments
dblock
changed the title
opensearchpy.exceptions.RequestError
opensearchpy.exceptions.RequestError: Illegal character ((CTRL-CHAR, code 31)): only regular white space (\\r, \\n, \\t) is allowed between tokens
Oct 24, 2023
(Edited the issue to be titled with the actual error, which is "'Illegal character ((CTRL-CHAR, code 31)): only regular white space (\r, \n, \t) is allowed between tokens"). @mmansour do you have a step-by-step repro, please? what are you sending to OpenSearch? |
Sorry I don't. It would be hard to create one in this case.
It kept happening on every rerun of a script that pulls data from external
resources.
The upserted JSON looked valid on the offending records.
Not sure what was happening. But in my scenario it made sense to just
downgrade to the version of opensearch that was working last month.
…On Tue, Oct 24, 2023 at 9:38 AM Daniel (dB.) Doubrovkine < ***@***.***> wrote:
@mmansour <https://github.com/mmansour> do you have a step-by-step repro,
please?
—
Reply to this email directly, view it on GitHub
<#10747 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGRODQU5QCEPT4HSWWX2ZLYA7VITAVCNFSM6AAAAAA6HLP7ROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZXGYYTMMJVHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yeah that looks like the one.
Thank you!
…On Tue, Oct 24, 2023 at 9:52 AM Daniel (dB.) Doubrovkine < ***@***.***> wrote:
I think #10802
<#10802> is the
same thing and has a lot of detail. I'm going to close this one. Can you
please confirm they are the same problem @mmansour
<https://github.com/mmansour>?
—
Reply to this email directly, view it on GitHub
<#10747 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGRODVTYXZTQJ5VG2ZGIA3YA7W5PAVCNFSM6AAAAAA6HLP7ROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZXGY2DGOBZGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
zyclove
added a commit
to zyclove/vanna
that referenced
this issue
May 13, 2024
olafhappy
pushed a commit
to olafhappy/vanna_ai
that referenced
this issue
Jul 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
On v 2.11.0 I am getting this error when upserting to latest using opensearch.py... When I downgrade to version 2.9.0 it works fine.
The text was updated successfully, but these errors were encountered: