Skip to content
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

MaxBytesLengthExceededException #26

Open
poom opened this issue Oct 26, 2016 · 3 comments
Open

MaxBytesLengthExceededException #26

poom opened this issue Oct 26, 2016 · 3 comments

Comments

@poom
Copy link

poom commented Oct 26, 2016

IllegalArgumentException[Document contains at least one immense term in field="response" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped. Please correct the analyzer to not produce such terms. The prefix of the first immense term is: '[123, 34, 115, 116, 97, 116, 117, 115, 34, 58, 50, 48, 48, 44, 34, 100, 97, 116, 97, 34, 58, 91, 123, 34, 105, 100, 34, 58, 49, 48]...', original message: bytes can be at most 32766 in length; got 465638]; nested: MaxBytesLengthExceededException[bytes can be at most 32766 in length; got 465638];

Can you have optional for truncate message or put original data to non-indexed field and truncate the message in indexed field?

@emsearcy
Copy link
Owner

Upstream issue Graylog2/graylog2-server#873

@emsearcy emsearcy reopened this Nov 23, 2016
@emsearcy
Copy link
Owner

If you have a chance to to review my truncate-strings branch, that would be great. I haven't tested it yet, but as soon as I have a chance to, I plan to merge it into master.

@emsearcy
Copy link
Owner

truncate-strings wasn't supposed to be merged; I've reverted it to un-break the master branch.

@emsearcy emsearcy reopened this Feb 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants