make the header not changed when do optimization
- Dominant language
- Rust
- Stars
- 9.3k
- Forks
- 2.4k
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 344
Description
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
(This section helps Arrow developers understand the context and *why* for this feature, in addition to the *what*)
In thist pr https://github.com/apache/arrow-datafusion/pull/3444
we provide a discussion about the header of the result.
The result always changes if do some optimization.
I have be stucked by this issue for doing this pr https://github.com/apache/arrow-datafusion/pull/3396
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
Contributor guide
Research direction
Start by reading the discussions in PR #3444 and the related work in PR #3396, which describe how optimization changes the result header. Reproduce the behavior in the current DataFusion query engine and trace the optimization path to identify where the header changes. Done means the result header remains unchanged after optimization, with regression coverage for the reported case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, sql
- Domain
- backend, data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100