JingsongLi commented on PR #11263:
URL: https://github.com/apache/paimon/pull/11263#issuecomment-7001169381

   Could you scope “only takes effect” to Flink-managed **row buffering**? In 
the Flink 1 writer harness, an ordinary append table with buffering off used 
zero buffer pages, but enabling `sink.use-managed-memory-allocator` still 
declared an operator managed-memory weight and received a 4 MiB managed-memory 
budget in the writer job graph. With buffering enabled, the same writer used 
pages from that budget and emitted committables. All 18 writer and memory cases 
passed with this additional control.
   
   The option controls allocator selection and the declared weight. 
`write-buffer-for-append` controls whether ordinary append records use that 
pool. Clarifying both effects would help operators reason about memory shares 
in a slot.
   


-- 
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]

Reply via email to