Re: Re: Duplicate operators generated by plan

2020-12-07 Thread Rex Fenley
Version 1.11.2 On Sun, Dec 6, 2020 at 10:20 PM Yun Gao wrote: > Hi Rex, > >I tried a similar example[1] but did not reproduce the issue, which > version of Flink you are using now ? > > Best, > Yun > > > > > [1] The example code: > > StreamExecutionEnvironment bsEnv = > StreamExecutionEnvi

Re: Re: Duplicate operators generated by plan

2020-12-06 Thread Yun Gao
Hi Rex, I tried a similar example[1] but did not reproduce the issue, which version of Flink you are using now ? Best, Yun [1] The example code: StreamExecutionEnvironment bsEnv = StreamExecutionEnvironment.getExecutionEnvironment(); bsEnv.setRestartStrategy(RestartStrategies.noRestart())

Re: Duplicate operators generated by plan

2020-12-03 Thread Rex Fenley
cc Brad On Thu, Dec 3, 2020 at 10:17 PM Rex Fenley wrote: > Yes, the same exact input operators go into both joins. > > The chunk of code for the joins from the specific part of the plan I > showed is as follows. The orgUsersTable is later filtered into one table > and aggregated and another tab

Re: Duplicate operators generated by plan

2020-12-03 Thread Rex Fenley
Yes, the same exact input operators go into both joins. The chunk of code for the joins from the specific part of the plan I showed is as follows. The orgUsersTable is later filtered into one table and aggregated and another table and aggregated. The planner seems to duplicate orgUsersTable into 2

Re: Duplicate operators generated by plan

2020-12-03 Thread Yun Gao
Hi Rex, Could you also attach one example for these sql / table ? And one possible issue to confirm is that does the operators with the same names also have the same inputs ? Best, Yun --Original Mail -- Sender:Rex Fenley Send Date:Fri Dec 4 02:55:41 2020