The last deploy on Next, is now discarding completely elasticsearch transactions calls when binary content is used and it's above the limit of 32766.
Using text content it works as before, it keeps the transaction log with the first 32766 chunk of data.
2024-06-20T09:00:57.451Z ERROR 1 --- [gateway] [nt-635-thread-5] o.a.dil.event.store.impl.ElasticStore : Failed to store event into elasticsearch. Reason: method [POST], host [http://flux-es-test:9200], URI [/transactions/_doc], status line [HTTP/1.1 400 Bad Request]
{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Document contains at least one immense term in field=\"body.keyword\" (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: '[45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 65, 115]...', original message: bytes can be at most 32766 in length; got 56845"}],"type":"illegal_argument_exception","reason":"Document contains at least one immense term in field=\"body.keyword\" (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: '[45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 45, 65, 115]...', original message: bytes can be at most 32766 in length; got 56845","caused_by":{"type":"max_bytes_length_exceeded_exception","reason":"bytes can be at most 32766 in length; got 56845"}},"status":400}
The last deploy on Next, is now discarding completely elasticsearch transactions calls when binary content is used and it's above the limit of 32766. Using text content it works as before, it keeps the transaction log with the first 32766 chunk of data.