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

Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/03 22:00:32 UTC

[GitHub] [beam] kennknowles opened a new issue, #19022: Boundedness and Unboundedness as a trait of a Rel so we know during planning

kennknowles opened a new issue, #19022:
URL: https://github.com/apache/beam/issues/19022

   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.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org