I figured it out. TableEnvironment.StatementSet. Semi-related, query optimizers can mess up the reuse depending on which tables the join IDs come from.
On Fri, Sep 18, 2020 at 9:40 PM Dan Hill <quietgol...@gmail.com> wrote: > I have a few results that I want to produce. > - A join B > - A join B join C > - A join B join C join D > - A join B join C join D join E > > When I use the DataSet API directly, I can execute all of these in the > same job to reduce redundancy. When I use the SQL interface, it looks like > separate jobs are created for each of these (duplicating join calculations). > > Is there a way to merge these joins? >
