Re: NPE in blink planner code gen

2019-12-15 Thread Benchao Li
Hi Jingsong, Leonard, Thanks for your response, I'll created an issue ( https://issues.apache.org/jira/browse/FLINK-15266) to track this. And further discussions can be moved to JIRA. Jingsong Li 于2019年12月16日周一 上午10:17写道: > Hi Benchao, > > Thanks for your reporting. > As Leonard said, you can c

Re: NPE in blink planner code gen

2019-12-15 Thread Jingsong Li
Hi Benchao, Thanks for your reporting. As Leonard said, you can create an issue in JIRA. We can go on discussing in JIRA. The answer is #1, Blink's behavior ensures that the job runs as much as possible without interrupting it, so null is returned here to make it possible to continue running. In

Re: NPE in blink planner code gen

2019-12-15 Thread Leonard Xu
Hi, Benchao, thank you for your report. It looks egacy planner and blink planner have different behavior. Could you create an issue in https://issues.apache.org/jira/browse/FLINK ? > On Dec 15, 2019, at 16:17, Benchao Li wrote: > > hi all, > > W

NPE in blink planner code gen

2019-12-15 Thread Benchao Li
hi all, We are using 1.9.0 blink planner, and find flink will throw NPE when we use the following SQL: ``` create table source { age int, id varchar }; select *case when age < 20 then cast(id as bigint) else 0 end* from source; ``` After debugging the Janino generated code, I find that NPE's