[ https://issues.apache.org/jira/browse/BEAM-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123271#comment-17123271 ]
Beam JIRA Bot commented on BEAM-4720: ------------------------------------- This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3. Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean. > Boundedness and Unboundedness as a trait of a Rel so we know during planning > ---------------------------------------------------------------------------- > > Key: BEAM-4720 > URL: https://issues.apache.org/jira/browse/BEAM-4720 > Project: Beam > Issue Type: New Feature > Components: dsl-sql > Reporter: Kenneth Knowles > Priority: P2 > Labels: stale-P2 > > 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. -- This message was sent by Atlassian Jira (v8.3.4#803005)