RocMarshal commented on PR #25218:
URL: https://github.com/apache/flink/pull/25218#issuecomment-2874816057

   > @RocMarshal are you planning to forward-port this as well? Or how do we 
ensure that we don't have a regression between 1.x and 2.x?
   
   Thanks @XComp 
   As described in the background of our previous email discussion:
   
   - The current fix is intended for the 1.x series branches that are still 
under maintenance.
   - It's acceptable to port this patch to the currently maintained versions in 
the 1.x series.
   - For the 2.x series, porting this patch is not being considered (at least 
that was the consensus during the discussion).   
   
   Based on historical comments, similar features in the 2.x series are 
expected to be introduced through a FLIP in order to achieve a more complete 
and reasonable design.
   
   Therefore, this issue still exists in the 2.x series branches, and there is 
currently no plan to fix it.
   Of course, this doesn't mean the patch can't be ported to the 2.x series.
   
   At the moment, we have two candidate approaches for supporting this feature 
in the 2.x series:
   - Introduce a more comprehensive and well-designed solution for 2.x based on 
a new FLIP.
   - Or directly port the current patch as-is.
   
   Please let me know your thoughts.
   
   CC @1996fanrui @ferenc-csaky @mxm 


-- 
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: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to