[Flink][Feature]Support task run not by jni call but use velox loop #3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
KevinyhZou
changed the title
Merged
zhanglistar
reviewed
Dec 2, 2025
| RowVectorPtr StatefulTask::next(int32_t& retCode) { | ||
| retCode = 0; | ||
| initOperators(); | ||
| // initOperators(); |
zhanglistar
reviewed
Dec 2, 2025
| } else { | ||
| break; | ||
| // break; | ||
| return nullptr; |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
在过去的实现中， 执行gluten flink 任务， task的运行时通过operator 在执行processElement的时候，逐条的调用jni 通过velox 的task执行来获取结果，性能较差。
此处通过替换该逻辑，通过velox 中C++的单线程的循环代替jni调用，减少性能损失。