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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
