imbajin commented on issue #3046: URL: https://github.com/apache/hugegraph/issues/3046#issuecomment-4622443562
@LegendPei Thanks, I assigned this issue to you. I agree this is a reasonable scoped improvement, but let's keep it simple and avoid over-designing it. Please focus on making the single `BytesBuffer` max capacity configurable while keeping the current default behavior. Suggested scope: - Add a `CoreOptions` config such as `serializer.buffer_max_capacity`, defaulting to the current 128MB. - Use the configured value in `BytesBuffer` capacity checks and related `LZ4Util` logic. - Keep a reasonable upper bound and make error messages show the effective limit. - Add focused unit tests and update the sample config/docs if needed. Note: this option should be treated as the max capacity of one serialization buffer, not as a general solution for huge exports. Large exports should still rely on paging/streaming when possible. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
