Huang Xingbo created FLINK-24933:
Summary: Support ML Python API
Key: FLINK-24933
URL: https://issues.apache.org/jira/browse/FLINK-24933
Project: Flink
Issue Type: New Feature
Hi Wenlong, I'm fine with the config options.
Best,
Godfrey
wenlong.lwl 于2021年11月17日周三 下午3:13写道：
>
> Hi Chesney and Konstantin,
> thanks for your feedback, I have added a section about How we support set
> description at DataStream API in the doc.
>
>
> Bests,
> Wenlong
>
> On Tue, 16 Nov 2021
Hi Chesney and Konstantin,
thanks for your feedback, I have added a section about How we support set
description at DataStream API in the doc.
Bests,
Wenlong
On Tue, 16 Nov 2021 at 21:05, Konstantin Knauf wrote:
> Hi everyone,
>
> Thanks for starting this discussion. I am in favor of solving
Congratulations, Jing!
Best,
Lincoln Lee
Jing Zhang 于2021年11月17日周三 上午10:24写道：
> Thanks to everyone. It's my honor to work in community with you all.
>
> Best,
> Jing Zhang
>
> Zakelly Lan 于2021年11月17日周三 上午12:06写道：
>
> > Congratulations, Jing!
> >
> > Best,
> > Zakelly
> >
> > On Tue, Nov
Congratulations!
Best,
Lincoln Lee
Zhilong Hong 于2021年11月17日周三 下午2:23写道：
> Congratulations, Yiingjie!
>
>
> Best regards,
> Zhilong
>
> On Wed, Nov 17, 2021 at 2:13 PM Yuepeng Pan wrote:
>
> > Congratulations !
> >
> >
> > Best,
> > Yuepeng Pan.
> >
> >
> > At 2021-11-17 12:55:29, "Guowei
Yun Tang created FLINK-24932:
Summary: Frocksdb cannot run on Apple M1
Key: FLINK-24932
URL: https://issues.apache.org/jira/browse/FLINK-24932
Project: Flink
Issue Type: Bug
Congratulations, Yiingjie!
Best regards,
Zhilong
On Wed, Nov 17, 2021 at 2:13 PM Yuepeng Pan wrote:
> Congratulations !
>
>
> Best,
> Yuepeng Pan.
>
>
> At 2021-11-17 12:55:29, "Guowei Ma" wrote:
> >Hi everyone,
> >
> >On behalf of the PMC, I'm very happy to announce Yingjie Cao as a new
>
Congratulations !
Best,
Yuepeng Pan.
At 2021-11-17 12:55:29, "Guowei Ma" wrote:
>Hi everyone,
>
>On behalf of the PMC, I'm very happy to announce Yingjie Cao as a new Flink
>committer.
>
>Yingjie has submitted 88 PRs since he joined the Flink community for more
>than 2 years. In general, his
Congratulations and welcome on board!
Best,
Yangze Guo
On Wed, Nov 17, 2021 at 1:26 PM Yun Gao wrote:
>
> Congratulations Yingjie!
>
> Best,
> Yun
>
>
>
> --Original Mail --
> Sender:Lijie Wang
> Send Date:Wed Nov 17 13:22:09 2021
> Recipients:Flink Dev
>
Congratulations Yingjie!
Best,
Yun
--Original Mail --
Sender:Lijie Wang
Send Date:Wed Nov 17 13:22:09 2021
Recipients:Flink Dev
Subject:Re: [ANNOUNCE] New Apache Flink Committer - Yingjie Cao
Congratulations Yingjie !
Guowei Ma 于2021年11月17日周三 下午12:56写道：
>
Congratulations Yingjie !
Guowei Ma 于2021年11月17日周三 下午12:56写道：
> Hi everyone,
>
> On behalf of the PMC, I'm very happy to announce Yingjie Cao as a new Flink
> committer.
>
> Yingjie has submitted 88 PRs since he joined the Flink community for more
> than 2 years. In general, his main
Hi everyone,
On behalf of the PMC, I'm very happy to announce Yingjie Cao as a new Flink
committer.
Yingjie has submitted 88 PRs since he joined the Flink community for more
than 2 years. In general, his main contributions are concentrated in
Flink's Shuffle. Yingjie has done a lot of work in
Yuepeng Pan created FLINK-24931:
---
Summary: Remove deprecated/unused class files in flink-scala
module.
Key: FLINK-24931
URL: https://issues.apache.org/jira/browse/FLINK-24931
Project: Flink
Shengkai Fang created FLINK-24930:
-
Summary: Print Sink should also print the table identifier when
output data
Key: FLINK-24930
URL: https://issues.apache.org/jira/browse/FLINK-24930
Project: Flink
Hi Flavio,
CDC connector's documentation is up-to-date. In fact, currently,
all released CDC connector versions are not compatible with Flink 1.14.
That's also mentioned by Thomas "the fact that X.Y.0 releases
tend to break downstream in one way or the other due to unexpected
upstream changes."
Yang Wang created FLINK-24929:
-
Summary: Kerberized YARN per-job on Docker test fails on Azure
because of building image
Key: FLINK-24929
URL: https://issues.apache.org/jira/browse/FLINK-24929
Project:
Thanks to everyone. It's my honor to work in community with you all.
Best,
Jing Zhang
Zakelly Lan 于2021年11月17日周三 上午12:06写道：
> Congratulations, Jing!
>
> Best,
> Zakelly
>
> On Tue, Nov 16, 2021 at 11:03 PM Yang Wang wrote:
>
>> Congratulations, Jing!
>>
>> Best,
>> Yang
>>
>> Benchao Li
Ingo Bürk created FLINK-24928:
-
Summary: Improve type-safety in Flink UI
Key: FLINK-24928
URL: https://issues.apache.org/jira/browse/FLINK-24928
Project: Flink
Issue Type: Sub-task
Ingo Bürk created FLINK-24927:
-
Summary: [Umbrella] Improvements for Flink UI
Key: FLINK-24927
URL: https://issues.apache.org/jira/browse/FLINK-24927
Project: Flink
Issue Type: Improvement
Hongbo created FLINK-24926:
--
Summary: Key group is not in KeyGroupRange when joining two
streams with table API
Key: FLINK-24926
URL: https://issues.apache.org/jira/browse/FLINK-24926
Project: Flink
bx123 created FLINK-24925:
-
Summary: SingleThreadAccessCheckingTypeSerializer#equals()
evaluates wrong field.
Key: FLINK-24925
URL: https://issues.apache.org/jira/browse/FLINK-24925
Project: Flink
Hi Jingsong!
Thank you for all the explanations. To follow up on the points:
(1) Log implementation
Good to hear you are looking to make this extensible.
(2) change tracking
Understood, makes sense (used for re-processing).
(3) Log Scan Startup mode.
Your explanation makes sense.
As I
Hi to all,
I'd like to point out that also official downstream-projects as CDC
connector's documentation should be updated to reflect compatibility with
new Flink releases[1].
The aforementioned link for example doesn't say nothing about which version
is compatible with Flink 1.14
[1]
Congratulations, Fabian
Best,
Zakelly
On Tue, Nov 16, 2021 at 11:21 PM liwei li wrote:
> Congratulations Fabian :-)
>
> Piotr Nowojski 于2021年11月16日周二 下午11:16写道：
>
> > Congratulations :)
> >
> > wt., 16 lis 2021 o 16:04 Yang Wang napisał(a):
> >
> > > Congratulations Fabian!
> > >
> > > Best,
Congratulations, Jing!
Best,
Zakelly
On Tue, Nov 16, 2021 at 11:03 PM Yang Wang wrote:
> Congratulations, Jing!
>
> Best,
> Yang
>
> Benchao Li 于2021年11月16日周二 下午9:31写道：
>
> > Congratulations Jing~
> >
> > OpenInx 于2021年11月16日周二 下午1:58写道：
> >
> > > Congrats Jing!
> > >
> > > On Tue, Nov 16,
Congratulations Fabian :-)
Piotr Nowojski 于2021年11月16日周二 下午11:16写道：
> Congratulations :)
>
> wt., 16 lis 2021 o 16:04 Yang Wang napisał(a):
>
> > Congratulations Fabian!
> >
> > Best,
> > Yang
> >
> > Fabian Paul 于2021年11月16日周二 下午3:57写道：
> >
> > > Thanks for the warm welcome, I am looking
Congratulations :)
wt., 16 lis 2021 o 16:04 Yang Wang napisał(a):
> Congratulations Fabian!
>
> Best,
> Yang
>
> Fabian Paul 于2021年11月16日周二 下午3:57写道：
>
> > Thanks for the warm welcome, I am looking forward to continuing
> > working with you all.
> >
> > Best,
> > Fabian
> >
>
Congratulations Fabian!
Best,
Yang
Fabian Paul 于2021年11月16日周二 下午3:57写道：
> Thanks for the warm welcome, I am looking forward to continuing
> working with you all.
>
> Best,
> Fabian
>
Congratulations, Jing!
Best,
Yang
Benchao Li 于2021年11月16日周二 下午9:31写道：
> Congratulations Jing~
>
> OpenInx 于2021年11月16日周二 下午1:58写道：
>
> > Congrats Jing!
> >
> > On Tue, Nov 16, 2021 at 11:59 AM Terry Wang wrote:
> >
> > > Congratulations, Jing!
> > > Well deserved!
> > >
> > > Best,
> > >
Congratulations Yangze~
Dawid Wysakowicz 于2021年11月15日周一 下午10:28写道：
> Congrats!
>
> On 15/11/2021 15:22, Marios Trivyzas wrote:
> > Congrats Yangze!
> >
> > On Mon, Nov 15, 2021 at 1:34 PM Martijn Visser
> > wrote:
> >
> >> Congrats Yangze!
> >>
> >> On Mon, 15 Nov 2021 at 09:13, Yangze Guo
Congratulations Leonard~
Yun Gao 于2021年11月16日周二 下午3:48写道：
> Congratulations Leonard!
>
> Best,
> Yun
>
>
> --
> From:Terry Wang
> Send Time:2021 Nov. 16 (Tue.) 14:27
> To:dev
> Cc:Dawid Wysakowicz
> Subject:Re: [ANNOUNCE] New
Congratulations Jing~
OpenInx 于2021年11月16日周二 下午1:58写道：
> Congrats Jing!
>
> On Tue, Nov 16, 2021 at 11:59 AM Terry Wang wrote:
>
> > Congratulations, Jing!
> > Well deserved!
> >
> > Best,
> > Terry Wang
> >
> >
> >
> > > 2021年11月16日 上午11:27，Zhilong Hong 写道：
> > >
> > > Congratulations,
Hi everyone,
Thanks for starting this discussion. I am in favor of solving this for
DataStream and Table API at the same time, using the same configuration
keys. IMO we shouldn't introduce any additional fragmentation if we can
avoid it.
Cheers,
Konstantin
On Tue, Nov 16, 2021 at 1:50 PM
Francesco Guardiani created FLINK-24924:
---
Summary: TO_TIMESTAMP and TO_DATE should fail
Key: FLINK-24924
URL: https://issues.apache.org/jira/browse/FLINK-24924
Project: Flink
Issue
hi, Chesney, we focus on sql first because the operator and topology of sql
jobs are generated by the engine, raising most of the problems in naming,
not only because the name is long but also because the topology can be more
complex than DataStream.
The case in Datastream is much better, most of
ozan created FLINK-24923:
Summary: Flink v1.13.2 restarts itself while Tenable Nessus
Vulnerability scans the machines
Key: FLINK-24923
URL: https://issues.apache.org/jira/browse/FLINK-24923
Project: Flink
Why should this be specific to the table API? The datastream API has
similar issues with long operator names (like windowing).
On 16/11/2021 11:22, wenlong.lwl wrote:
Thanks Godfrey for the suggestion.
Regarding 1, how about table.optimizer.simplify-operator-name-enabled,
which means that we
> On the other hand I am a silent fan of the current PR template because
> it also provides a summary of the PR to make it easier for committers
> to determine the impacts.
I 100% agree that part of a PR (and thus the template) should be the
summary of the what, why, and how of the changes. I
Thanks Godfrey for the suggestion.
Regarding 1, how about table.optimizer.simplify-operator-name-enabled,
which means that we would simplify the name of operator and keep the
details in description only.
"table.optimizer.operator-name.description-enabled" can not describe what
it means I think.
xiangqiao created FLINK-24922:
-
Summary: Fix spelling errors in the word "parallism"
Key: FLINK-24922
URL: https://issues.apache.org/jira/browse/FLINK-24922
Project: Flink
Issue Type: Bug
Hi all,
Maybe I am the devil's advocate but I see the stability of master and
the definition of done as disjunct properties. I think it is more a
question of prioritization that test instabilities are treated as
critical tickets and have to be addressed before continuing any other
work. It will
Thanks for creating this FLIP Wenlong.
The FLIP already looks pretty solid, I think the config options can be
improved a little:
1) about table.optimizer.separate-name-and-description, I think
"operator-name" should be considered in the option,
how about
Hi all,
Thanks for bringing this up for this discussion, because I think it's an
important aspect.
>From my perspective, a 'definition of done' serves two purposes:
1. It informs the contributor on what's expected when making a contribution
in the form of a PR
2. It instructs the committer on
I don't have any strong opinions on the asserting framework that we use,
but big +1 for the unification.
Best,
D.
On Tue, Nov 16, 2021 at 9:37 AM Till Rohrmann wrote:
> Using JUnit5 with assertJ is fine with me if the community agrees. Having
> guides for best practices would definitely help
Etienne Chauchot created FLINK-24921:
Summary: FileSourceSplit should not be visible in the user API in
ParquetColumnarRowInputFormat
Key: FLINK-24921
URL: https://issues.apache.org/jira/browse/FLINK-24921
Martijn Visser created FLINK-24920:
--
Summary: Update README
Key: FLINK-24920
URL: https://issues.apache.org/jira/browse/FLINK-24920
Project: Flink
Issue Type: Sub-task
Reporter:
Using JUnit5 with assertJ is fine with me if the community agrees. Having
guides for best practices would definitely help with the transition.
Cheers,
Till
On Mon, Nov 15, 2021 at 5:34 PM Francesco Guardiani
wrote:
> > It is a bit unfortunate that we have tests that follow different
>
Piotr Nowojski created FLINK-24919:
--
Summary: UnalignedCheckpointITCase hangs on Azure
Key: FLINK-24919
URL: https://issues.apache.org/jira/browse/FLINK-24919
Project: Flink
Issue Type: Bug
Hi Reuven,
this would be a great addition to the Flink Runner and could help with
broader adoption ;)
to make an effective implementation that works well across different state
backends, this will most likely require adding a new primitive state type
to the Flink's state backend ecosystem. I'll
+1 with Ingo proposal, the goal of the template should be to help developer
to do a self check of his/her PR quality, not to define whether something
is done or not. It's up to the committer to check that the "definition of
done" is fulfilled.
> The Definition of Done as suggested:
This
50 matches
Mail list logo
