4paradigm / 4paradigm/OpenMLDB
Fail to add and remove columns for InternalRow when enabling UnsafeRowOpt
Open
batch-engine
bug
- Dominant language
- C++
- Stars
- 1.7k
- Forks
- 331
- Avg merge
- 12d 12h
- Merged PRs (30d)
- 1
Description
Now all the last join test cases will fail if we use UnsafeRowOpt to add and remove extra columns.
So we cannot enable unsaferow and other optimiztions at the same time.
Contributor guide
Research direction
The issue mentions failing join test cases when UnsafeRowOpt is enabled for adding/removing columns on InternalRow. Start by locating the join tests and the UnsafeRowOpt implementation. Examine how column operations interact with InternalRow. Run the failing tests to see the specific errors, then trace the code paths for adding/removing columns in unsafe row mode.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100