CarlosJuncher03 opened a new issue, #8563: URL: https://github.com/apache/hop/issues/8563
### What would you like to happen? When Apache Hop stores Execution Information in PostgreSQL, large values in fields such as: childExecutionData -> all-transforms -> ExecutionData -> rowsBinaryGzipBase64Encoded can exceed the default Jackson StreamReadConstraints maximum string length of 20,000,000 characters. Example error: String value length (20054016) exceeds the maximum allowed (20000000, from StreamReadConstraints.getMaxStringLength()) The execution itself may continue, but the Execution Information data may not be fully persisted once this internal JSON parser limit is exceeded. The expected behavior is that Apache Hop should still be able to persist and retrieve the complete Execution Information payload in PostgreSQL even when rowsBinaryGzipBase64Encoded is larger than 20,000,000 characters. This limit should not prevent the Execution Information from being stored. Possible improvements could include: Making the Jackson maximum string length configurable in Apache Hop. Supporting payloads larger than the default Jackson limit. Splitting large Execution Data payloads into smaller chunks before persistence. Using streaming or another storage strategy that avoids processing the entire Base64 content as a single JSON string. PostgreSQL itself is capable of storing values larger than this limit, so the current restriction appears to be related to the internal JSON serialization/deserialization process rather than the database storage capacity. The main goal of this improvement is to ensure that large Execution Information records are fully persisted instead of being skipped or partially lost because of the Jackson string-size limit. ### Issue Priority Priority: 3 ### Issue Component Component: Hop Gui, Component: Infrastructure -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
