You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/06/03 22:01:00 UTC

[jira] [Commented] (BEAM-4720) Boundedness and Unboundedness as a trait of a Rel so we know during planning

    [ https://issues.apache.org/jira/browse/BEAM-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17547254#comment-17547254 ] 

Kenneth Knowles commented on BEAM-4720:
---------------------------------------

This issue has been migrated to https://github.com/apache/beam/issues/19022

> 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: P3
>
> 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.20.7#820007)