Boundedness and Unboundedness as a trait of a Rel so we know during planning
Open
dsl
new feature
P3
sql
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
Currently we do not know the boundedness or unboundedness of a collection until after planning is complete, so it cannot influence the plan. Instead, BeamJoinRel makes post-planning decisions about what sort of join to implement. We should move this into the planning phase. I think Calcite traits are the intended way to do this.
Imported from Jira [BEAM-4720](https://issues.apache.org/jira/browse/BEAM-4720). Original Jira may contain additional context.
Reported by: kenn.
Contributor guide
Assessment
This issue has not been assessed yet.