[C++] Migrate existing usage of ThreadIndexer to ThreadLocalState and get rid of ThreadIndexer
- Dominant language
- C++
- Stars
- 17.1k
- Forks
- 4.3k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 91
Description
ARROW-16178 introduces a better way of doing thread indexing. Once ARROW-15732 is resolved then we can get rid of the old way and migrate to the new approach.
**Reporter**: [Weston Pace](https://issues.apache.org/jira/browse/ARROW-16179) / @westonpace
#### Related issues:
- [[C++] Do not use any CPU threads in execution plan when use_threads is false](https://github.com/apache/arrow/issues/31181) (is blocked by)
**Note**: *This issue was originally created as [ARROW-16179](https://issues.apache.org/jira/browse/ARROW-16179). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Read ARROW-16178 to understand ThreadLocalState and check the status of ARROW-15732 before starting. Search the repository for existing ThreadIndexer usage, including the execution-plan context from issue 31181; done means those usages are migrated and ThreadIndexer can be removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100