Jianhui Dong created FLINK-25273:
Summary: Some doubts about the FLINK-22848
Key: FLINK-25273
URL: https://issues.apache.org/jira/browse/FLINK-25273
Project: Flink
Issue Type: Improvement
Thanks, Yufeng, for starting this discussion. I think this will be a very
popular feature. I've seen a lot of users asking for this in the past. So,
generally big +1.
I think we should have a rough idea on how to expose this feature in the
other APIs.
Two ideas:
1. In order to make this more det
Jianhui Dong created FLINK-25272:
Summary: Flink sql syntax analysis is inconsistent with the sql
grammer declared now
Key: FLINK-25272
URL: https://issues.apache.org/jira/browse/FLINK-25272
Project:
+1
I didn't think this was necessary when I published the blog post on Friday,
but this has made higher waves than I expected over the weekend.
On Mon, Dec 13, 2021 at 8:23 AM Yuan Mei wrote:
> +1 for quick release.
>
> On Mon, Dec 13, 2021 at 2:55 PM Martijn Visser
> wrote:
>
> > +1 to addr
+1 for quick release.
On Mon, Dec 13, 2021 at 2:55 PM Martijn Visser
wrote:
> +1 to address the issue like this
>
> On Mon, 13 Dec 2021 at 07:46, Jingsong Li wrote:
>
> > +1 for fixing it in these versions and doing quick releases. Looks good
> to
> > me.
> >
> > Best,
> > Jingsong
> >
> > On M
Yun Gao created FLINK-25271:
---
Summary: ApplicationDispatcherBootstrapITCase.
testDispatcherRecoversAfterLosingAndRegainingLeadership failed on azure
Key: FLINK-25271
URL: https://issues.apache.org/jira/browse/FLINK-2527
Yun Gao created FLINK-25270:
---
Summary: Azure failed due to stopped hearing from agent
AlibabaCI006-agent01
Key: FLINK-25270
URL: https://issues.apache.org/jira/browse/FLINK-25270
Project: Flink
Is
Yun Gao created FLINK-25269:
---
Summary: Quickstarts Scala nightly end-to-end test failed on azure
due to could not connect to resource manager
Key: FLINK-25269
URL: https://issues.apache.org/jira/browse/FLINK-25269
+1 to address the issue like this
On Mon, 13 Dec 2021 at 07:46, Jingsong Li wrote:
> +1 for fixing it in these versions and doing quick releases. Looks good to
> me.
>
> Best,
> Jingsong
>
> On Mon, Dec 13, 2021 at 2:18 PM Becket Qin wrote:
> >
> > +1. The solution sounds good to me. There have
+1 for fixing it in these versions and doing quick releases. Looks good to me.
Best,
Jingsong
On Mon, Dec 13, 2021 at 2:18 PM Becket Qin wrote:
>
> +1. The solution sounds good to me. There have been a lot of inquiries
> about how to react to this.
>
> Thanks,
>
> Jiangjie (Becket) Qin
>
> On Mo
Hi Timo,
+1 for the improvement.
Best,
Godfrey
Timo Walther 于2021年12月10日周五 20:37写道：
>
> Hi Wenlong,
>
> yes it will. Sorry for the confusion. This is a logical consequence of
> the assumption:
>
> The JSON plan contains no implementation details (i.e. no classes) and
> is fully declarative.
>
>
+1. The solution sounds good to me. There have been a lot of inquiries
about how to react to this.
Thanks,
Jiangjie (Becket) Qin
On Mon, Dec 13, 2021 at 12:40 PM Prasanna kumar <
prasannakumarram...@gmail.com> wrote:
> 1+ for making Updates for 1.12.5 .
> We are looking for fix in 1.12 version.
Junfan Zhang created FLINK-25268:
Summary: Support task manager node-label in Yarn deployment
Key: FLINK-25268
URL: https://issues.apache.org/jira/browse/FLINK-25268
Project: Flink
Issue Type
1+ for making Updates for 1.12.5 .
We are looking for fix in 1.12 version.
Please notify once the fix is done.
On Mon, Dec 13, 2021 at 9:45 AM Leonard Xu wrote:
> +1 for the quick release and the special vote period 24h.
>
> > 2021年12月13日 上午11:49，Dian Fu 写道：
> >
> > +1 for the proposal and cre
+1 for the quick release and the special vote period 24h.
> 2021年12月13日 上午11:49，Dian Fu 写道：
>
> +1 for the proposal and creating a quick release.
>
> Regards,
> Dian
>
>
> On Mon, Dec 13, 2021 at 11:15 AM Kyle Bendickson wrote:
>
>> +1 to doing a release for this widely publicized vulnerabi
I like the idea. It can reuse the disk to do many things. Isn't it only for
inner failover? If not, the cleaning may be a problem. Also, many resource
components have their own disk schedule strategy.
Chesnay Schepler 于2021年12月12日周日 19:59写道：
> How do you intend to handle corrupted files, in part
+1 for the proposal and creating a quick release.
Regards,
Dian
On Mon, Dec 13, 2021 at 11:15 AM Kyle Bendickson wrote:
> +1 to doing a release for this widely publicized vulnerability.
>
> In my experience, users will often update to the latest minor patch version
> without much fuss. Plus, u
Congratulations!
Best
Liu Jiangang
Nicholas Jiang 于2021年12月13日周一 11:28写道：
> Congratulations, Ingo!
>
> Best,
> Nicholas Jiang
>
Congratulations!
Best
Liu Jiangang
Nicholas Jiang 于2021年12月13日周一 11:23写道：
> Congratulations, Matthias!
>
> Best,
> Nicholas Jiang
>
Any progress on the feature? We have the same requirement in our company.
Since the soft and hard environment can be complex, it is normal to see a
slow task which determines the execution time of the flink job.
于2021年6月20日周日 22:35写道：
> Hi everyone,
>
> I would like to kick off a discussion on s
Hi Martijn,
IMO, in this FLIP, we only need to introduce the general design of the Table
API/SQL level. As for the design details, you can create a new FLIP. And do we
need to take into account the support for Batch mode if you expand the
MATCH_RECOGNIZE function? About the dynamic rule engi
Congratulations, Matthias!
Best,
Nicholas Jiang
Congratulations, Ingo!
Best,
Nicholas Jiang
+1 to doing a release for this widely publicized vulnerability.
In my experience, users will often update to the latest minor patch version
without much fuss. Plus, users have also likely heard about this and will
appreciate a simple fix (updating their version where possible).
The work-around wi
Congratulations!
On Fri, Dec 10, 2021 at 7:58 PM Zhilong Hong wrote:
> Congratulations, Ingo!
>
> Best,
> Zhilong
>
> On Wed, Dec 8, 2021 at 10:18 PM godfrey he wrote:
>
> > Congratulations, Ingo!
> >
> > Best,
> > Godfrey
> >
> > Roman Khachatryan 于2021年12月6日周一 下午6:07写道：
> > >
> > > Congratul
Congratulations!
On Fri, Dec 10, 2021 at 8:00 PM Zhilong Hong wrote:
> Congratulations, Matthias!
>
> Best,
> Zhilong
>
> On Wed, Dec 8, 2021 at 10:18 PM godfrey he wrote:
>
> > Congratulations, Matthias!
> >
> > Best,
> > Godfrey
> >
> > Roman Khachatryan 于2021年12月6日周一 下午6:07写道：
> > >
> > > C
Kerem Ulutaş created FLINK-25267:
Summary: Unable to (always) recover using checkpoint in HA setup
(both Zookeeper and Kubernetes)
Key: FLINK-25267
URL: https://issues.apache.org/jira/browse/FLINK-25267
Hi all!
Without doubt, you heard about the log4j vulnerability [1].
There is an advisory blog post on how to mitigate this in Apache Flink [2],
which involves setting a config option and restarting the processes. That
is fortunately a relatively simple fix.
Despite this workaround, I think we sh
Chesnay Schepler created FLINK-25266:
Summary: StreamingKafkaITCase fails with incorrect number of
messages
Key: FLINK-25266
URL: https://issues.apache.org/jira/browse/FLINK-25266
Project: Flink
coco created FLINK-25265:
Summary: RUNNING to FAILED with failure cause. This might indicate
that the remote task manager was lost.
Key: FLINK-25265
URL: https://issues.apache.org/jira/browse/FLINK-25265
Proj
How do you intend to handle corrupted files, in particular due to
process crashes during a write?
Will all writes to a cached directory append some suffix (e.g.,
".pending") and do a rename?
On 10/12/2021 17:54, Till Rohrmann wrote:
Hi everyone,
I would like to start a discussion about introd
coco created FLINK-25264:
Summary: Does the binlog_row_image of MySQL must be in full mode
when Flink CDC is used?
Key: FLINK-25264
URL: https://issues.apache.org/jira/browse/FLINK-25264
Project: Flink
Chesnay Schepler created FLINK-25263:
Summary: KafkaSourceE2ECase is broken
Key: FLINK-25263
URL: https://issues.apache.org/jira/browse/FLINK-25263
Project: Flink
Issue Type: Technical De
33 matches
Mail list logo
