+1 to try the bot solution and see how it goes.
On Fri, Jan 11, 2019 at 6:54 AM jincheng sun
wrote:
> +1 for the bot solution!
> and I think Timo‘s suggestion is very useful!
> Thanks,
> Jincheng
>
>
> Timo Walther 于2019年1月11日 周五22:44写道:
>
> > Thanks for bringing up this discussion again. +1
Hi,
this is a known problem that occurs if you have big expressions. For
example, a big CASE WHEN clause. Currenlty, we only split by field not
within expressions. But this might be fixed soon as there is a PR
available [1].
As a workaround, use a UDF instead.
Regards,
Timo
[1]
+1 for the bot solution!
and I think Timo‘s suggestion is very useful!
Thanks,
Jincheng
Timo Walther 于2019年1月11日 周五22:44写道:
> Thanks for bringing up this discussion again. +1 for a bot solution.
> However, we should discuss a good process for closing PRs.
>
> In many cases, PRs are closed not
Thanks for bringing up this discussion again. +1 for a bot solution.
However, we should discuss a good process for closing PRs.
In many cases, PRs are closed not because the contributor did not
respond but because no committer prioritizes the PR high enough. Or the
PR has issues that might
tivanli created FLINK-11308:
---
Summary: flink sql In the case when statement has a large in
statement error: class DataStreamCalcRule$1933 grows beyond 64 KB
Key: FLINK-11308
URL:
Gary Yao created FLINK-11307:
Summary: Set up nightly to run Tests with Java 9
Key: FLINK-11307
URL: https://issues.apache.org/jira/browse/FLINK-11307
Project: Flink
Issue Type: Test
+1 for the stable bot, as it will help bring valuable PR out to be reviewed.
> On Jan 11, 2019, at 6:26 PM, Driesprong, Fokko wrote:
>
> +1 I'm in favor of the Stale bot.
>
> We use the Stalebot at Apache Airflow as well, and it really helps smoothen
> the reviewing process. Keep in mind that
+1 I'm in favor of the Stale bot.
We use the Stalebot at Apache Airflow as well, and it really helps smoothen
the reviewing process. Keep in mind that the number of PR's processed by
the Stalebot is limited at each run. So you won't get a gazillion
notifications, but just a few every couple of
Fokko Driesprong created FLINK-11306:
Summary: Bump derby from 10.10.1.1 to 10.14.2.0
Key: FLINK-11306
URL: https://issues.apache.org/jira/browse/FLINK-11306
Project: Flink
Issue Type:
Hi,
Welcome to the Flink community.
I gave you contributor permissions for Jira.
Best, Fabian
Am Fr., 11. Jan. 2019 um 07:02 Uhr schrieb Jary Zhen :
> Hey,
> I’d like to apply for dev authority, Here is my jira account is : JaryZhen
>
> Thinks
>
10 matches
Mail list logo