+1 (non-binding) from my side
Best,
Godfrey
Leonard Xu 于2020年8月4日周二 上午11:07写道:
> Hi all,
>
> I would like to start the vote for FLIP-132 [1], which has been discussed
> and
> reached a consensus in the discussion thread [2].
>
> The vote will be open until 7th August (72h), unless there is an
Benchao Li created FLINK-18837:
--
Summary: Allow retract message for StreamSelectTableSink
Key: FLINK-18837
URL: https://issues.apache.org/jira/browse/FLINK-18837
Project: Flink
Issue Type: Impro
Dian Fu created FLINK-18838:
---
Summary: Support JdbcCatalog in Python Table API
Key: FLINK-18838
URL: https://issues.apache.org/jira/browse/FLINK-18838
Project: Flink
Issue Type: Improvement
+1 on my side for feature freeze date by the end of Oct.
--
From:Yuan Mei
Send Time:2020年8月6日(星期四) 14:54
To:dev
Subject:Re: [DISCUSS] Planning Flink 1.12
+1
> +1 for extending the feature freeze date to the end of October.
On
Dian Fu created FLINK-18839:
---
Summary: Add documentation about how to use catalog in Python
Table API
Key: FLINK-18839
URL: https://issues.apache.org/jira/browse/FLINK-18839
Project: Flink
Issue T
Hi All,
It has been more than 2 months since we released Flink 1.10.1. We already
have more than 60 resolved improvements/bugs in the release-1.10 branch.
Therefore, I propose to create the next bugfix release 1.10.2 for Flink
1.10.
Most noticeable fixes are:
- FLINK-18663 RestServerEndpoint may
Hello,
We are using Apache Flink 1.10.1 version. During our security scans following
issues are reported by our scan tool.
Please let us know your comments on these dependency vulnerabilities.
Thanks,
Suchithra
-Original Message-
From: m...@gsuite.cloud.apache.org On Behalf Of
Apache
log4j - If you don't use a Socket appender, you're good. Otherwise, you
can replace the log4j jars in lib/ with a newer version. You could also
upgrade to 1.11.1 which uses log4j2.
guava - We do not use Guava for serialization AFAIK. We also do not use
Java serialization for records.
commons
Thanks for kicking this discussion off Zhu Zhu. +1 for the 1.10.2 release.
Also thanks for volunteering as the release manager!
Cheers,
Till
On Thu, Aug 6, 2020 at 1:26 PM Zhu Zhu wrote:
> Hi All,
>
> It has been more than 2 months since we released Flink 1.10.1. We already
> have more than 60
Timo Walther created FLINK-18840:
Summary: Support StatementSet with DataStream API
Key: FLINK-18840
URL: https://issues.apache.org/jira/browse/FLINK-18840
Project: Flink
Issue Type: New Feat
Jeff Hu created FLINK-18841:
---
Summary: CVE-2018-10237 and CWE-400 occurred in flink dependency
Key: FLINK-18841
URL: https://issues.apache.org/jira/browse/FLINK-18841
Project: Flink
Issue Type: Bu
Dian Fu created FLINK-18842:
---
Summary: e2e test failed to download "localhost:/flink.tgz"
Key: FLINK-18842
URL: https://issues.apache.org/jira/browse/FLINK-18842
Project: Flink
Issue Type: Test
Hi Roman,
Indeed there are more frequent checkpoints with this change! The
application was configured to checkpoint every 10s. With 1.10 ("good
commit"), that leads to fewer completed checkpoints compared to 1.11 ("bad
commit"). Just to be clear, the only difference between the two runs was
the co
Zhang Jianguo created FLINK-18843:
-
Summary: Flink WEB-UI ISSUE
Key: FLINK-18843
URL: https://issues.apache.org/jira/browse/FLINK-18843
Project: Flink
Issue Type: Bug
Affects Versions: 1.
jinxin created FLINK-18844:
--
Summary: support maxwell-json for Maxwell binlog collector
Key: FLINK-18844
URL: https://issues.apache.org/jira/browse/FLINK-18844
Project: Flink
Issue Type: Improvement
HuiyuZhou created FLINK-18845:
-
Summary: class not found exception when i use sql client to try
mysql as datasource.
Key: FLINK-18845
URL: https://issues.apache.org/jira/browse/FLINK-18845
Project: Flink
Jark Wu created FLINK-18846:
---
Summary: Set a meaningful operator name for the filesystem sink
Key: FLINK-18846
URL: https://issues.apache.org/jira/browse/FLINK-18846
Project: Flink
Issue Type: Impr
Thanks for taking care of this Zhu Zhu. The list of bugs from your list
certainly justifies pushing out a bugfix release.
I would propose to wait until Monday for people to speak up if they want to
have a fix included in the release. Otherwise, we could create the first RC
on Monday evening (China
Thanks for volunteering as the release manager, zhuzhu.
+1 for the 1.10.2 release and I am willing to provide any help in the procedure
if needing PMC permission operations.
Best,
Zhijiang
--
From:Robert Metzger
Send Time:2020年
Thank you all for the confirmation and suggestion.
And thanks Zhijiang for offering the PMC power to help with the release.
Robert's suggestion sounds good to me. I will keep watching the ML and
JIRA issues until next Monday evening. If there were no new concerns
nor blocking issues, I will start
20 matches
Mail list logo