Hi Tanjialiang,
Like we discussed in another thread, please feel free to create a FLIP and
start further discussion. In case you need any access right to the wiki
page, please let me know, thanks.
Best regards,
Jing
On Sun, Apr 23, 2023 at 4:23 AM tanjialiang wrote:
> Hi, devs.
> Do anyone ha
Hi, devs.
Do anyone has any question about this discussion? I'm looking forwards to your
feedback.
Best regards,
tanjialiang.
Replied Message
| From | tanjialiang |
| Date | 4/13/2023 10:05 |
| To | dev@flink.apache.org |
| Subject | [DISCUSS] EncodingFormat and DecondingFormat prov
Hi, Aitozi,
Thanks you for your feedback, and +1 for your point of view.
Best,
tanjialiang.
Replied Message
| From | Aitozi |
| Date | 4/14/2023 16:19 |
| To | |
| Subject | Re: [DISCUSS] EncodingFormat and DecondingFormat provide copy API |
Hi tanjialiang
Thanks for reporting this, I
Hi tanjialiang
Thanks for reporting this, I think it's a reasonable requirements.
The problem might be introduced during the optimization when
reusing the mutable state in Source. So the DecodingFormat#copy can
avoid this situation.
But after checking the related code for DynamicTableSink,
