原来你是小幸运001 created FLINK-32540:
--
Summary: The issue of not distributing the last batch of data
Key: FLINK-32540
URL: https://issues.apache.org/jira/browse/FLINK-32540
Project: Flink
Issue Type:
Hi, Piotr & Dong.
Thanks for the discussion.
IMO, I do not think the provided counter proposal is a good idea. There are
some concerns from my side.
1. It is hard to find the error checkpoint.
If there are other errors causing the checkpoint failure, we have to check
every failed checkpoint to f
Congrats and cheers!
Best,
Paul Lam
> 2023年7月4日 18:04，Benchao Li 写道：
>
> Congratulations!
>
> Feng Jin 于2023年7月4日周二 16:17写道：
>
>> Congratulations!
>>
>> Best,
>> Feng Jin
>>
>>
>>
>> On Tue, Jul 4, 2023 at 4:13 PM Yuxin Tan wrote:
>>
>>> Congratulations!
>>>
>>> Best,
>>> Yuxin
>>>
>
Thanks all for the discussion.
It seems to me there's a consensus on marking the following as deprecated
in 1.18:
- DataSet API
- SourceFunction
- Queryable State
- All Scala APIs
More time is needed for deprecating SinkFunction.
I'll leave this discussion open for a few more days. And if there'
Thanks for the input, Jing. I'd also be +1 for option 1.
Best,
Xintong
On Mon, Jul 3, 2023 at 7:20 PM Jing Ge wrote:
> Hi Xingtong,
>
> Option 1, secure plan would be:
>
> 1. graduate kafka, File, JDBC connectors to @Public
> 2. graduate SinkV2 to @Public
> 3. remove SinkFunction.
>
> Option
Sergey Nuyanzin created FLINK-32539:
---
Summary: Archunit violations started to fail in test_misc
Key: FLINK-32539
URL: https://issues.apache.org/jira/browse/FLINK-32539
Project: Flink
Issue
Hi Aitozi,
I think it is necessary to add the following description in FLIP to express the
difference between user-defined asynchronous table function and
AsyncTableFunction:
User-defined asynchronous table functions allow complex parameters (e.g., Row
type) to be passed to function, which is
Yuxin Tan created FLINK-32538:
-
Summary: CI build failed because node is corrupted when compiling
Key: FLINK-32538
URL: https://issues.apache.org/jira/browse/FLINK-32538
Project: Flink
Issue Type
Hi ConradJam,
I think Chesnay has already put his name as the Contributor for the two
tasks you listed. Maybe you can reach out to him to see if you can
collaborate on this.
In general, I don't think contributing to a release 2.0 issue is much
different from contributing to a regular issue. We ha
Hi Piotr,
Any suggestion on how we can practically move forward to address the target
use-case?
My understanding is that the current proposal does not have any
correctness/performance issues. And it allows the extension to support all
the extra use-case without having to throw away the proposed A
Hi all,
I've tried to migrate my very simple Elasticsearch SourceFunction (that
use scroll API and produce batch of documents) to new Source API, but I
gave up because it's too complicated. It should much simpler to migrate
that function to a bounded or unbounded source.
Before removing completely
Hi Xuannan, Hi Dong
Thanks for the Proposal! After reading the FLIP, I'd like to ask some
questions:
1. Naming convention for boolean variables. It is recommended to follow
JavaBean [1], i.e. objectReuseCompliant as the variable name with
isObjectReuseCompliant() and setObjectReuseCompliant() as
Thanks Dian Fu for sharing the externalized connector usage within
flink-python.
Looking forward to the solution to this problem, and if possible, can
participate in the contribution of this problem,
and thank you Martijn for the dependency usage that the externalized
connector should follow.
Bes
Hong Liang Teoh created FLINK-32537:
---
Summary: Add compatibility annotation for REST API classes
Key: FLINK-32537
URL: https://issues.apache.org/jira/browse/FLINK-32537
Project: Flink
Issue
Hi Samrat,
The dependency between JDBC and AWS worries me a lot: we're already seeing
that coupling causes a lot of issues down the line. Why can't we decouple
these?
Best regards,
Martijn
On Tue, Jul 4, 2023 at 3:35 PM Samrat Deb wrote:
> Hi Leonard,
>
> Sorry for the late reply.
>
> > 1 Reu
Hi Leonard,
Sorry for the late reply.
> 1 Reusing the capabilities of JDBC and Filesystem in the Redshift
connector generally makes sense to me. However, since all of them are
managed in different repositories and depend on Flink dependency, could you
explain how you establish the versioning, rel
Chesnay Schepler created FLINK-32536:
Summary: Python tests fail with Arrow DirectBuffer exception
Key: FLINK-32536
URL: https://issues.apache.org/jira/browse/FLINK-32536
Project: Flink
I
Hong Liang Teoh created FLINK-32535:
---
Summary: CheckpointingStatisticsHandler periodically returns
NullArgumentException after job restarts
Key: FLINK-32535
URL: https://issues.apache.org/jira/browse/FLINK-32535
Thanks Ran Tao for proposing this discussion and Martijn for sharing
the thought.
> While flink-python now fails the CI, it shouldn't actually depend on the
externalized connectors. I'm not sure what PyFlink does with it, but if
belongs to the connector code,
For each DataStream connector, there
> waiting 2 min between 2 requirements push seems ok to me
This depends on the workload. Would you care if the cost of rescaling were
close to zero (which is for most out-of-the-box workloads)? In that case,
it would be desirable to rescale more frequently, for example, if TMs join
incrementally.
Sergey Nuyanzin created FLINK-32534:
---
Summary: exit code 137 (i.e. OutOfMemoryError) in flink-tests
module
Key: FLINK-32534
URL: https://issues.apache.org/jira/browse/FLINK-32534
Project: Flink
Sergey Nuyanzin created FLINK-32533:
---
Summary: exit code 137 (i.e. OutOfMemoryError) in python module
Key: FLINK-32533
URL: https://issues.apache.org/jira/browse/FLINK-32533
Project: Flink
Sergey Nuyanzin created FLINK-32532:
---
Summary: exit code 137 (i.e. OutOfMemoryError) in
flink-s3-fs-hadoop module
Key: FLINK-32532
URL: https://issues.apache.org/jira/browse/FLINK-32532
Project: Fli
Hi all,
Thanks David for your feedback. My comments are inline
Le 04/07/2023 à 09:16, David Morávek a écrit :
They will struggle if they add new resources and nothing happens for 5
minutes.
The same applies if they start playing with FLIP-291 APIs. I'm wondering if
the cooldown makes sense th
I think the cooldown still makes sense with FLIP-291 APIs.
If you want to fully control the parallelism and rescale timings then
you can set the cooldown to zero.
If you don't want complete control but just the target parallelism from
time to time, then the cooldown within Flink still makes sen
Congratulations!
Feng Jin 于2023年7月4日周二 16:17写道：
> Congratulations!
>
> Best,
> Feng Jin
>
>
>
> On Tue, Jul 4, 2023 at 4:13 PM Yuxin Tan wrote:
>
> > Congratulations!
> >
> > Best,
> > Yuxin
> >
> >
> > Dunn Bangui 于2023年7月4日周二 16:04写道：
> >
> > > Congratulations!
> > >
> > > Best,
> > > Bangui
Ivan Stoiev created FLINK-32531:
---
Summary: "Recovery of missing job deployments" feature not working
as described
Key: FLINK-32531
URL: https://issues.apache.org/jira/browse/FLINK-32531
Project: Flink
Jacky Lau created FLINK-32530:
-
Summary: array_position semantic should align with array_contains
instead of spark
Key: FLINK-32530
URL: https://issues.apache.org/jira/browse/FLINK-32530
Project: Flink
Hi all,
@David, I just saw your comments on the [DISCUSSION] thread. I'll close
this vote for now and open a new voting thread when the discussion
reaches a consensus.
Best
Etienne
Le 04/07/2023 à 10:49, Etienne Chauchot a écrit :
Hi David,
Indeed, this thread was a proper separate [VOTE
Gyula Fora created FLINK-32529:
--
Summary: Optional startup probe for JM deployment
Key: FLINK-32529
URL: https://issues.apache.org/jira/browse/FLINK-32529
Project: Flink
Issue Type: New Feature
Hi David,
Indeed, this thread was a proper separate [VOTE] thread 😁
You withdrew your -1 vote but did not cast a new vote. Can you do so ?
Thanks
Etienne
Le 04/07/2023 à 08:52, David Morávek a écrit :
Hmm, sorry for the confusion; it seems that Google is playing games with me
(I see this cha
LakeShen created FLINK-32528:
Summary: The RexCall a = a,if a's datatype is nullable, and when a
is null, a = a is null, it isn't true in BinaryComparisonExprReducer
Key: FLINK-32528
URL: https://issues.apache.org/jir
Fangbin Sun created FLINK-32527:
---
Summary: Build failure on Windows
Key: FLINK-32527
URL: https://issues.apache.org/jira/browse/FLINK-32527
Project: Flink
Issue Type: Bug
Components:
Congratulations!
Best,
Feng Jin
On Tue, Jul 4, 2023 at 4:13 PM Yuxin Tan wrote:
> Congratulations!
>
> Best,
> Yuxin
>
>
> Dunn Bangui 于2023年7月4日周二 16:04写道：
>
> > Congratulations!
> >
> > Best,
> > Bangui Dunn
> >
> > Yangze Guo 于2023年7月4日周二 15:59写道：
> >
> > > Congrats everyone!
> > >
> > >
Congratulations!
Best,
Yuxin
Dunn Bangui 于2023年7月4日周二 16:04写道：
> Congratulations!
>
> Best,
> Bangui Dunn
>
> Yangze Guo 于2023年7月4日周二 15:59写道：
>
> > Congrats everyone!
> >
> > Best,
> > Yangze Guo
> >
> > On Tue, Jul 4, 2023 at 3:53 PM Rui Fan <1996fan...@gmail.com> wrote:
> > >
> > > Congrat
Sergey Nuyanzin created FLINK-32526:
---
Summary: Update apache parquet to 1.31.1
Key: FLINK-32526
URL: https://issues.apache.org/jira/browse/FLINK-32526
Project: Flink
Issue Type: Technical D
Congratulations!
Best,
Bangui Dunn
Yangze Guo 于2023年7月4日周二 15:59写道：
> Congrats everyone!
>
> Best,
> Yangze Guo
>
> On Tue, Jul 4, 2023 at 3:53 PM Rui Fan <1996fan...@gmail.com> wrote:
> >
> > Congratulations!
> >
> > Best,
> > Rui Fan
> >
> > On Tue, Jul 4, 2023 at 2:08 PM Zhu Zhu wrote:
> >
Congrats everyone!
Best,
Yangze Guo
On Tue, Jul 4, 2023 at 3:53 PM Rui Fan <1996fan...@gmail.com> wrote:
>
> Congratulations!
>
> Best,
> Rui Fan
>
> On Tue, Jul 4, 2023 at 2:08 PM Zhu Zhu wrote:
>
> > Congratulations everyone!
> >
> > Thanks,
> > Zhu
> >
> > Hang Ruan 于2023年7月4日周二 14:06写道：
> >
I've left some comments on the PR.
On Tue, Jul 4, 2023 at 9:20 AM Martijn Visser
wrote:
> Hi Hong,
>
> Given that this changes the REST API, which is a public interface, I'm
> wondering if this shouldn't first have had a (small) FLIP if I follow the
> guidelines from the overview page [1].
>
> B
Congratulations!
Best,
Rui Fan
On Tue, Jul 4, 2023 at 2:08 PM Zhu Zhu wrote:
> Congratulations everyone!
>
> Thanks,
> Zhu
>
> Hang Ruan 于2023年7月4日周二 14:06写道：
> >
> > Congratulations!
> >
> > Best,
> > Hang
> >
> > Jingsong Li 于2023年7月4日周二 13:47写道：
> >
> > > Congratulations!
> > >
> > > Thank
Martijn Visser created FLINK-32525:
--
Summary: Update commons-beanutils to 1.9.4
Key: FLINK-32525
URL: https://issues.apache.org/jira/browse/FLINK-32525
Project: Flink
Issue Type: Technical D
Hi Hong,
Given that this changes the REST API, which is a public interface, I'm
wondering if this shouldn't first have had a (small) FLIP if I follow the
guidelines from the overview page [1].
Best regards,
Martijn
[1]
https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposal
> They will struggle if they add new resources and nothing happens for 5
minutes.
The same applies if they start playing with FLIP-291 APIs. I'm wondering if
the cooldown makes sense there since it was the user's deliberate choice to
push new requirements. 🤔
Best,
D.
On Tue, Jul 4, 2023 at 9:11
The FLIP reads sane to me. I'm unsure about the default values, though; 5
minutes of wait time between rescales feels rather strict, and we should
rethink it to provide a better out-of-the-box experience.
I'd focus on newcomers trying AS / Reactive Mode out. They will struggle if
they add new reso
44 matches
Mail list logo
