t; System.out.println(ret.explain());
>
> DataStream> row = bsTableEnv.toRetractStream(ret,
> Row.class);
> row.addSink(new SinkFunction>() {
>@Override
> public void invoke(Tuple2 value, Context context) throws
> Exception {
>
>}
> });
>
> System.out.println(bsEnv.getStreamGraph().getStreamingPlanAsJSON());
>
row = bsTableEnv.toRetractStream(ret,
Row.class);
row.addSink(new SinkFunction>() {
@Override
public void invoke(Tuple2 value, Context context) throws
Exception {
}
});
System.out.println(bsEnv.getStreamGraph().getStreamingPlanAsJSON());
----------
Sen
etResultType(signature: Array[Class[_]]):
> TypeInformation[_] =
> Types.ROW(
> Types.LONG,
> Types.BOOLEAN,
> Types.BOOLEAN,
> Types.BOOLEAN,
> Types.BOOLEAN
> )
> }
>
>
> On Thu, Dec 3, 2020 at 7:49 PM Yun Gao wrote:
>
>> Hi Rex,
>>
>>
OOLEAN,
Types.BOOLEAN,
Types.BOOLEAN
)
}
On Thu, Dec 3, 2020 at 7:49 PM Yun Gao wrote:
> 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 ?
>
&g
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
Hello,
I'm running into an issue where my execution plan is creating the same
exact join operator multiple times simply because the subsequent operator
filters on a different boolean value. This is a massive duplication of
storage and work. The filtered operators which follow result in only a
smal
