+1 (binding)
Best
Yun Tang
On 2021/11/24 07:50:15 Sergey Nuyanzin wrote:
> +1 (non-binding)
>
> On Wed, Nov 24, 2021 at 8:38 AM godfrey he wrote:
>
> > +1 (binding)
> >
> > Best,
> > Godfrey
> >
> > Jark Wu 于2021年11月24日周三 下午12:02写道：
> > >
> > > +1 (binding)
> > >
> > > Btw, @JingZhang I think
+1 (non-binding)
On Wed, Nov 24, 2021 at 8:38 AM godfrey he wrote:
> +1 (binding)
>
> Best,
> Godfrey
>
> Jark Wu 于2021年11月24日周三 下午12:02写道：
> >
> > +1 (binding)
> >
> > Btw, @JingZhang I think your vote can be counted into binding now.
> >
> > Best,
> > Jark
> >
> > On Tue, 23 Nov 2021 at 20:19
+1 (binding)
Best,
Godfrey
Jark Wu 于2021年11月24日周三 下午12:02写道：
>
> +1 (binding)
>
> Btw, @JingZhang I think your vote can be counted into binding now.
>
> Best,
> Jark
>
> On Tue, 23 Nov 2021 at 20:19, Jing Zhang wrote:
>
> > +1 (non-binding)
> >
> > Best,
> > Jing Zhang
> >
> > Martijn Visser 于
+1 (non-binding)
Best,
Lijie
Jark Wu 于2021年11月24日周三 下午12:01写道：
> +1 (binding)
>
> Btw, @JingZhang I think your vote can be counted into binding now.
>
> Best,
> Jark
>
> On Tue, 23 Nov 2021 at 20:19, Jing Zhang wrote:
>
> > +1 (non-binding)
> >
> > Best,
> > Jing Zhang
> >
> > Martijn Visser
刘方奇 created FLINK-25029:
---
Summary: Hadoop Caller Context Setting In Flink
Key: FLINK-25029
URL: https://issues.apache.org/jira/browse/FLINK-25029
Project: Flink
Issue Type: Improvement
Compon
+1 (binding)
Btw, @JingZhang I think your vote can be counted into binding now.
Best,
Jark
On Tue, 23 Nov 2021 at 20:19, Jing Zhang wrote:
> +1 (non-binding)
>
> Best,
> Jing Zhang
>
> Martijn Visser 于2021年11月23日周二 下午7:42写道：
>
> > +1 (non-binding)
> >
> > On Tue, 23 Nov 2021 at 12:13, Aitozi
wangbaohua created FLINK-25028:
--
Summary: java.lang.OutOfMemoryError: Java heap space
Key: FLINK-25028
URL: https://issues.apache.org/jira/browse/FLINK-25028
Project: Flink
Issue Type: Bug
> I also referred to the "no-claim" mode and I still think neither of them
> works in that mode, as you'd have to keep lineage of checkpoints externally
> to be able delete any checkpoint.
I think the lineage is needed in all approaches with arbitrary
histories; the difference is whether a runni
Thanks for digging into this.
Regarding this query:
INSERT INTO the_table
SELECT window_end, COUNT(*)
FROM (TUMBLE(TABLE interactions, DESCRIPTOR(ts), INTERVAL '5' MINUTES))
GROUP BY window_end
HAVING now() - window_end <= INTERVAL '14' DAYS;
I am not sure I understand what the conclusion
Nico Kruber created FLINK-25027:
---
Summary: Allow GC of a finished job's JobMaster before the slot
timeout is reached
Key: FLINK-25027
URL: https://issues.apache.org/jira/browse/FLINK-25027
Project: Flin
Till Rohrmann created FLINK-25026:
-
Summary:
UnalignedCheckpointRescaleITCase.shouldRescaleUnalignedCheckpoint fails on AZP
Key: FLINK-25026
URL: https://issues.apache.org/jira/browse/FLINK-25026
Proj
Till Rohrmann created FLINK-25025:
-
Summary:
BatchArrowPythonGroupWindowAggregateFunctionOperatorTest.testFinishBundleTriggeredByCount
failed on AZP
Key: FLINK-25025
URL: https://issues.apache.org/jira/browse/FLI
Roman Khachatryan created FLINK-25024:
-
Summary: Add ChangelogBackend documentation
Key: FLINK-25024
URL: https://issues.apache.org/jira/browse/FLINK-25024
Project: Flink
Issue Type: Sub-
Nico Kruber created FLINK-25023:
---
Summary: ClassLoader leak on JM/TM through indirectly-started
Hadoop threads out of user code
Key: FLINK-25023
URL: https://issues.apache.org/jira/browse/FLINK-25023
Pr
Nico Kruber created FLINK-25022:
---
Summary: ClassLoader leak with ThreadLocals on the JM when
submitting a job through the REST API
Key: FLINK-25022
URL: https://issues.apache.org/jira/browse/FLINK-25022
Xue Wang created FLINK-25021:
Summary: Source/Sink for Azure Data Explorer (ADX)
Key: FLINK-25021
URL: https://issues.apache.org/jira/browse/FLINK-25021
Project: Flink
Issue Type: New Feature
I think I know where the confusion comes from regarding arbitrarily
recovery histories: Both my counter-proposals were for "no-claim"
mode; I didn't mean to replace "claim" mode with them.
However, as Yun pointed out, it's impossible to guarantee that all the
files will be compa
Chesnay Schepler created FLINK-25020:
Summary: FlinkSecurityManager can swallow exception
Key: FLINK-25020
URL: https://issues.apache.org/jira/browse/FLINK-25020
Project: Flink
Issue Type
Chesnay Schepler created FLINK-25019:
Summary: Incorrect netty shading prefix
Key: FLINK-25019
URL: https://issues.apache.org/jira/browse/FLINK-25019
Project: Flink
Issue Type: Bug
Chesnay Schepler created FLINK-25018:
Summary: Upgrade Curator to 5.2.0
Key: FLINK-25018
URL: https://issues.apache.org/jira/browse/FLINK-25018
Project: Flink
Issue Type: Improvement
Chesnay Schepler created FLINK-25017:
Summary: Drop Zookeeper 3.4
Key: FLINK-25017
URL: https://issues.apache.org/jira/browse/FLINK-25017
Project: Flink
Issue Type: Improvement
Thanks Dawid, Yun and Piotr,
I think I know where the confusion comes from regarding arbitrarily
recovery histories: Both my counter-proposals were for "no-claim"
mode; I didn't mean to replace "claim" mode with them.
However, as Yun pointed out, it's impossible to guarantee that all the
files wil
Hi,
I'm not entirely sure if I fully understand the raised concerns here. So
let me maybe step back in the discussion a bit and address the original
points from Roman.
> 2. Instead of forcing re-upload, can we "inverse control" in no-claim
mode?
I second the concerns from Dawid. This is effectiv
Hi everyone,
continued support for Java 8 can also create project risks, e.g. if a
vulnerability arises in Flink's dependencies and we cannot upgrade them
because they no longer support Java 8. Some projects already started
deprecating support as well, like Kafka, and other projects will likely
fo
Chesnay Schepler created FLINK-25016:
Summary: Bump netty to 4.1.70
Key: FLINK-25016
URL: https://issues.apache.org/jira/browse/FLINK-25016
Project: Flink
Issue Type: Improvement
+1 (non-binding)
Best,
Jing Zhang
Martijn Visser 于2021年11月23日周二 下午7:42写道：
> +1 (non-binding)
>
> On Tue, 23 Nov 2021 at 12:13, Aitozi wrote:
>
> > +1 (non-binding)
> >
> > Best,
> > Aitozi
> >
> > wenlong.lwl 于2021年11月23日周二 下午4:00写道：
> >
> > > Hi everyone,
> > >
> > > Based on the discussion[
KevinyhZou created FLINK-25015:
--
Summary: job name should not always be `collect` submitted by sql
client
Key: FLINK-25015
URL: https://issues.apache.org/jira/browse/FLINK-25015
Project: Flink
Hi all,
My conclusion at this point is that there is consensus that the default
behaviour of CAST should raise errors when it fails and that it should be
configurable via a configuration flag.
The open discussion is on when we want to fix the current (incorrect)
behaviour:
1. Doing it in the nex
+1 (non-binding)
On Tue, 23 Nov 2021 at 12:13, Aitozi wrote:
> +1 (non-binding)
>
> Best,
> Aitozi
>
> wenlong.lwl 于2021年11月23日周二 下午4:00写道：
>
> > Hi everyone,
> >
> > Based on the discussion[1], we seem to have consensus, so I would like to
> > start a vote on FLIP-195 [2].
> > Thanks for all o
Some user has usage to restore different jobs based on a same
externalized checkpoint. I think this usage would break after
introducing this FLIP, and we must tell users explicitly if choose
to make Flink manage the checkpoints by default.
Could you elaborate what do you mean? The
Oliver Moser created FLINK-25014:
Summary: Table to DataStream conversion, wrong field order
Key: FLINK-25014
URL: https://issues.apache.org/jira/browse/FLINK-25014
Project: Flink
Issue Type:
+1 (non-binding)
Best,
Aitozi
wenlong.lwl 于2021年11月23日周二 下午4:00写道：
> Hi everyone,
>
> Based on the discussion[1], we seem to have consensus, so I would like to
> start a vote on FLIP-195 [2].
> Thanks for all of your feedback.
>
> The vote will last for at least 72 hours (Nov 26th 16:00 GMT) un
+1（non-binding）
Very helpful improvement!
Best,
Terry Wang
> 2021年11月23日 下午3:59，wenlong.lwl 写道：
>
> Hi everyone,
>
> Based on the discussion[1], we seem to have consensus, so I would like to
> start a vote on FLIP-195 [2].
> Thanks for all of your feedback.
>
> The vote will last for at le
zhangjg created FLINK-25013:
---
Summary: flink pulsar connector cannot consume deferred messages
Key: FLINK-25013
URL: https://issues.apache.org/jira/browse/FLINK-25013
Project: Flink
Issue Type: Bug
xiangqiao created FLINK-25012:
-
Summary: Cannot join hive tables with different column types
Key: FLINK-25012
URL: https://issues.apache.org/jira/browse/FLINK-25012
Project: Flink
Issue Type: Imp
Hi Thomas and Akshay,
Sorry for the late reply. Due to problems with other FLIPs, we had to scrap
our plans to publish FLIP-182 in Flink 1.14. However as far as I know,
Arvid is working on this right now, and we are tentatively aiming with this
feature for the 1.15.0 release. I hope Arvid will be
Hi,
Very thanks Wenlong for the update! Also +1 for the proposal~
Best,
Yun Gao
--
From:Yun Gao
Send Time:2021 Nov. 23 (Tue.) 16:09
To:dev
Subject:Re: [DISCUSS] Improve the name and structure of job vertex and operator
name for
Hi everyone,
Based on the discussion[1], we seem to have consensus, so I would like to
start a vote on FLIP-195 [2].
Thanks for all of your feedback.
The vote will last for at least 72 hours (Nov 26th 16:00 GMT) unless
there is an objection or insufficient votes.
[1] https://lists.apache.org/thr
38 matches
Mail list logo
