Hi Dong, Sorry for not seeing this initially. I did have one question about the description of the issue in the FLIP:
> However, in cases where the upstream and downstream operators do not store or > access references to the input or output records, this deep-copy overhead > becomes unnecessary I was interested in getting clarification as to what you meant by “or access references…”, to see if it covered this situation: StreamX —forward--> operator1 StreamX —forward--> operator2 If operator1 modifies the record, and object re-use is enabled, then operator2 will see the modified version, right? Thanks, — Ken > On Jul 2, 2023, at 7:24 PM, Xuannan Su <suxuanna...@gmail.com> wrote: > > Hi all, > > Dong(cc'ed) and I are opening this thread to discuss our proposal to > add operator attribute to allow operator to specify support for > object-reuse [1]. > > Currently, the default configuration for pipeline.object-reuse is set > to false to avoid data corruption, which can result in suboptimal > performance. We propose adding APIs that operators can utilize to > inform the Flink runtime whether it is safe to reuse the emitted > records. This enhancement would enable Flink to maximize its > performance using the default configuration. > > Please refer to the FLIP document for more details about the proposed > design and implementation. We welcome any feedback and opinions on > this proposal. > > Best regards, > > Dong and Xuannan > > [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=255073749 -------------------------- Ken Krugler http://www.scaleunlimited.com Custom big data solutions Flink & Pinot
