[C++] Switch bindings-scanner to the new scan node, remove the old scan node
- Dominant language
- C++
- Stars
- 17.1k
- Forks
- 4.3k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 91
Description
Once the new scan node is fully capable we should switch the language bindings (pyarrow / R) to use the new scan options. At this point we can get rid of the old scan node.
**Reporter**: [Weston Pace](https://issues.apache.org/jira/browse/ARROW-17756) / @westonpace
**Watchers**: [Rok Mihevc](https://issues.apache.org/jira/browse/ARROW-17756) / @rok
**Note**: *This issue was originally created as [ARROW-17756](https://issues.apache.org/jira/browse/ARROW-17756). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Start with the linked migration documentation and trace the bindings-scanner’s use of the new scan node and scan options in the PyArrow and R bindings. Confirm that the new scan node supports those bindings before switching them over. Done means the old scan node is no longer needed and has been removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python, r
- Domain
- data-engineering
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100