You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As Kyuubi supports multi-computing engines, some engines like Spark themselves do not report affected rows but some engines like JDBC do. We can start with the JDBC engine to let them report affected rows after completing the DML operations, and propagate to client side
Making changes in computing engines to allow them to report affected rows (this is the most challenging part of this task)
What's the level of this task?
CHALLENGE
Code of Conduct
Search before creating
Mentor
Skill requirements
Background and Goals
JDBC standard requires the following method return affected rows.
Hive added such a feature in 4.0.0 https://issues.apache.org/jira/browse/HIVE-14388
Implementation steps
This is an umbrella ticket to track all sub-tasks
numModifiedRows
inTGetOperationStatusResp
Additional context
Introduction of 2024H1 Kyuubi Code Contribution Program
The text was updated successfully, but these errors were encountered: