Hi, Au_Miner Thank you for your reply. I will address each question one by one. >1、当前是计划重新开发一套flink-extension模块以连接native-engine吗，据我所了解目前auron的jniBridge与spark-memory关联较为密切，需要在native-engine中对spark-memory进行解藕。是否有计划将spark-extension中的部分逻辑进行拆分，以实现二者的共享。 Yes, we have already introduced the Flink module into the Auron repository. In issue #1263 [1], we have completed the decoupling of some basic functionalities. Regarding the spark-memory related matters you mentioned, my understanding is limited to the on-heap spill component and its connection to Spark. We will continue to advance the decoupling efforts, which will be a long-term process.
>2、Calc Operator的native实现，是否有计划在前后添加r2c，c2r operator，这块的添加逻辑是否也有计划在flink的改造中添加接口 As Native operator coverage increases, standalone row/column transformation operators offer advantages in scenarios where multiple Native operators can be chained together. Only for Calc operator, embedding row/column transformations may prove more convenient. Of course, this approach is open for discussion. >3、当前对Flink的版本有选择吗，Flink的改造是否有接口的计划表（据我所了解需要在Phyiscal/ExecNode、Rule、Processor、OperatorChain等方面需要考虑） > We plan to start with Flink version 1.18. Among the companies I know of, the primary versions are 1.17 and 1.18. Currently, this initiative only involves the Auron community. Improvements for the Flink community will be initiated in the future, with no confirmed timeline at this time. 4、回撤类型、水位线、Checkpoint、时间服务、状态后端的支持可能是后续阶段的重点，是否有计划在native-engine中支持。 For Phase 1, stateless operators, watermarks, and checkpoints will be supported. Retract Message, TimeService, and state backends will not be supported; these will be supported in Phase 2. I hope this answers your question. I look forward to receiving more feedback. -- Best regards, Mang Zhang 在 2025-11-28 21:36:13，"Au_Miner" <[email protected]> 写道： >关于Flink SQL + Auron Collaboration有一些想法， > > >1、当前是计划重新开发一套flink-extension模块以连接native-engine吗，据我所了解目前auron的jniBridge与spark-memory关联较为密切，需要在native-engine中对spark-memory进行解藕。是否有计划将spark-extension中的部分逻辑进行拆分，以实现二者的共享。 > > >2、Calc Operator的native实现，是否有计划在前后添加r2c，c2r operator，这块的添加逻辑是否也有计划在flink的改造中添加接口 >3、当前对Flink的版本有选择吗，Flink的改造是否有接口的计划表（据我所了解需要在Phyiscal/ExecNode、Rule、Processor、OperatorChain等方面需要考虑） > 4、回撤类型、水位线、Checkpoint、时间服务、状态后端的支持可能是后续阶段的重点，是否有计划在native-engine中支持。
