Ensure ExecutionPlan nodes have unique names
Open
- Dominant language
- Rust
- Stars
- 9.3k
- Forks
- 2.4k
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 344
Description
1 more thing is probably we need to ensure the name is unique? if implementation will be separated across different crates and users can develop their own implementations it can possibly be that the name will not be unique for 2 different structs
_Originally posted by @comphead in https://github.com/apache/arrow-datafusion/pull/9793#pullrequestreview-1966518576_
Contributor guide
Research direction
Start by reviewing the ExecutionPlan node naming discussion in pull request 9793 and tracing how node structs are implemented across crates. Determine how names should remain unique for both built-in and user-defined implementations, then define completion as a documented, tested uniqueness guarantee.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100