Congratulations, Sergey!
Best regards,
Jane
On Wed, Feb 22, 2023 at 9:44 AM Dian Fu wrote:
> Congratulations Sergey!
>
> On Tue, Feb 21, 2023 at 9:07 PM Rui Fan wrote:
>
> > Congratulations, Sergey!
> >
> > Best
> > Rui Fan
> >
> > On Tue, Feb 21, 2023 at 20:55 Junrui Lee wrote:
> >
> > >
Matthias Pohl created FLINK-31180:
-
Summary: Fail early when installing minikube and check whether we
can retry
Key: FLINK-31180
URL: https://issues.apache.org/jira/browse/FLINK-31180
Project: Flink
Jingsong Lee created FLINK-31179:
Summary: Make data structures serializable
Key: FLINK-31179
URL: https://issues.apache.org/jira/browse/FLINK-31179
Project: Flink
Issue Type: Improvement
Jingsong Lee created FLINK-31178:
Summary: Public Writer API
Key: FLINK-31178
URL: https://issues.apache.org/jira/browse/FLINK-31178
Project: Flink
Issue Type: Improvement
Hi kui
Thanks for initializing this discussion. I have two questions
1. What will happen if we add watermark related options in `the connector
options`? Will the connector ignore these options or throw an exception?
How can we support this?
2. If one table is used by two operators with
CHEN Zhongpu created FLINK-31177:
Summary: To introduce a formatter for Markdown files
Key: FLINK-31177
URL: https://issues.apache.org/jira/browse/FLINK-31177
Project: Flink
Issue Type:
Congratulations, Anton!
Best regards,
Jane
On Wed, Feb 22, 2023 at 11:22 AM Yun Tang wrote:
> Congratulations, Anton!
>
> Best
> Yun Tang
>
> From: Dian Fu
> Sent: Wednesday, February 22, 2023 9:44
> To: dev@flink.apache.org
> Subject: Re: [ANNOUNCE] New
Congratulations, Rui!
Best regards,
Jane
On Wed, Feb 22, 2023 at 11:21 AM Yun Tang wrote:
> Congratulations, Rui!
>
> Best
> Yun Tang
>
> From: Dian Fu
> Sent: Wednesday, February 22, 2023 9:45
> To: dev@flink.apache.org
> Cc: rui fan <1996fan...@gmail.com>
>
Hi kui,
There is a scenario using watermark that cannot be implemented through SQL now：
We only support specify rowtime column in table DDL，if the rowtime field is
generated by join dimension table , it cannot be implemented
Can we consider implement through HINTS like :
Select * from t1 join
wangkang created FLINK-31176:
Summary: correct the description of sql gateway configuration
Key: FLINK-31176
URL: https://issues.apache.org/jira/browse/FLINK-31176
Project: Flink
Issue Type:
Congratulations, Anton!
Best
Yun Tang
From: Dian Fu
Sent: Wednesday, February 22, 2023 9:44
To: dev@flink.apache.org
Subject: Re: [ANNOUNCE] New Apache Flink Committer - Anton Kalashnikov
Congratulations Anton!
On Tue, Feb 21, 2023 at 9:12 PM Austin
Shengkai Fang created FLINK-31175:
-
Summary: Fix link doesn't work in hive_reaad_write doc
Key: FLINK-31175
URL: https://issues.apache.org/jira/browse/FLINK-31175
Project: Flink
Issue Type:
Congratulations, Rui!
Best
Yun Tang
From: Dian Fu
Sent: Wednesday, February 22, 2023 9:45
To: dev@flink.apache.org
Cc: rui fan <1996fan...@gmail.com>
Subject: Re: [ANNOUNCE] New Apache Flink Committer - Rui Fan
Congratulations Rui!
On Tue, Feb 21, 2023 at 6:34
CHEN Zhongpu created FLINK-31174:
Summary: [Doc] Inconsistent data format between
flink-training-repo and learn-flink doc
Key: FLINK-31174
URL: https://issues.apache.org/jira/browse/FLINK-31174
Thanks Kui for driving this topic.
I think this FLIP could help users leverage the ability of watermark alignment
in Flink SQL when backfilling the data, which is helpful to use stream
applications to replace batch applications.
Best
Yun Tang
From: kui yuan
Zhipeng Zhang created FLINK-31173:
-
Summary: TailOperator should only have one input
Key: FLINK-31173
URL: https://issues.apache.org/jira/browse/FLINK-31173
Project: Flink
Issue Type: Bug
Hi devs,
I'd like to start a discussion thread for FLIP-296[1]. This comes from an
offline discussion with @Yun Tang, and we hope to enrich table API & SQL to
support many watermark-related features which were only implemented at the
datastream API level.
Basically, we want to introduce
Thank you all for the feedback. Point taken about decoupling content/structure
and design. As a first step, I can work with an AWS UX designer and come with a
list of suggestions and wireframes. And while we aren't forming a committee
yet, if anyone wants to collaborate, please reach out.
On
Congratulations Rui!
On Tue, Feb 21, 2023 at 6:34 PM Maximilian Michels wrote:
> Congrats Rui! Well done!!
>
> -Max
>
> On Tue, Feb 21, 2023 at 10:09 AM Roman Khachatryan
> wrote:
> >
> > Congratulations Rui!
> >
> > Regards,
> > Roman
> >
> >
> > On Mon, Feb 20, 2023 at 5:58 PM Anton
Congratulations Anton!
On Tue, Feb 21, 2023 at 9:12 PM Austin Cawley-Edwards <
austin.caw...@gmail.com> wrote:
> Congrats Anton 拾
>
> On Tue, Feb 21, 2023 at 04:08 Roman Khachatryan wrote:
>
> > Congratulations Anton, well deserved!
> >
> > Regards,
> > Roman
> >
> >
> > On Tue, Feb 21, 2023 at
Congratulations Sergey!
On Tue, Feb 21, 2023 at 9:07 PM Rui Fan wrote:
> Congratulations, Sergey!
>
> Best
> Rui Fan
>
> On Tue, Feb 21, 2023 at 20:55 Junrui Lee wrote:
>
> > Congratulations Sergey!
> >
> > weijie guo 于2023年2月21日周二 20:54写道：
> >
> > > Congratulations, Sergey~
> > >
> > > Best
Dian Fu created FLINK-31172:
---
Summary: Support coGroup in Python DataStream API
Key: FLINK-31172
URL: https://issues.apache.org/jira/browse/FLINK-31172
Project: Flink
Issue Type: New Feature
Dian Fu created FLINK-31171:
---
Summary: Support iterate in Python DataStream API
Key: FLINK-31171
URL: https://issues.apache.org/jira/browse/FLINK-31171
Project: Flink
Issue Type: New Feature
Hi Timo, Thanks.
yes. We need to make Flink's implementation of this feature more scalable
and versatile.
I will try to update this FLIP on the comparison and difference of the
implementation of some features
on other popular or commercial engines you mentioned.
Let us see how to find a better
Hi Ran,
adding additional filter and selection capabilities makes sense.
However, I would recommend to not only check Spark or Hive but also
focus on bigger commercial players such as Snowflake, Oracle, SQL Server.
In any case, maybe we should also investigate more thoughts on a Flink
Hi Ran,
When you're creating your FLIP, please also have a look at Calcite SQL
parser, since that's used by Flink [1]
Best regards,
Martijn
[1] https://calcite.apache.org/docs/reference.html
On Tue, Feb 21, 2023 at 2:10 PM Ran Tao wrote:
> Yes, I totally agree with your point. The current
Max is raising some good points.
Ultimately, you are free to propose changes; we don't categorically
reject changes to the website.
On the flip-side, the proposed changes should also be as granular as
possible, because there's no real reason why changing the content
structure should be
Thank you, Gyula.
+1 (non-binding)
I tested the following:
1. Downloaded the archives, checksums, signatures and README file
2. Build the source distribution to ensure all source files have Apache headers
3. Verify that all POM files point to the same version
4. Helm repo install from
BoYi Zhang created FLINK-31170:
--
Summary: The spelling error of the document word causes sql to
fail to execute
Key: FLINK-31170
URL: https://issues.apache.org/jira/browse/FLINK-31170
Project: Flink
Congrats Anton 拾
On Tue, Feb 21, 2023 at 04:08 Roman Khachatryan wrote:
> Congratulations Anton, well deserved!
>
> Regards,
> Roman
>
>
> On Tue, Feb 21, 2023 at 9:34 AM Martijn Visser
> wrote:
>
> > Congratulations Anton!
> >
> > On Tue, Feb 21, 2023 at 8:08 AM Lincoln Lee
> > wrote:
> >
>
Yes, I totally agree with your point. The current flink sql syntax is tiled
together without classification.
Let me try to summarize these four categories, not just Auxiliary
Statements. And compare it with other popular engines.
Thank you, Jing !
Best Regards,
Ran Tao
Thank you, Gyula.
+1 (binding)
- Verified Helm repo works as expected, points to correct image tag, build,
version
- Verified basic examples + checked operator logs everything looks as
expected
- Verified hashes, signatures and source release contains no binaries
- Ran built-in tests, built jars
Congratulations, Sergey!
Best
Rui Fan
On Tue, Feb 21, 2023 at 20:55 Junrui Lee wrote:
> Congratulations Sergey!
>
> weijie guo 于2023年2月21日周二 20:54写道：
>
> > Congratulations, Sergey~
> >
> > Best regards,
> >
> > Weijie
> >
> >
> > Jing Ge 于2023年2月21日周二 20:52写道：
> >
> > > congrats Sergey!
> >
Matthias Pohl created FLINK-31169:
-
Summary: KubernetesResourceManagerDriverTest fails fatally due to
239 exit code
Key: FLINK-31169
URL: https://issues.apache.org/jira/browse/FLINK-31169
Project:
Congratulations Sergey!
weijie guo 于2023年2月21日周二 20:54写道：
> Congratulations, Sergey~
>
> Best regards,
>
> Weijie
>
>
> Jing Ge 于2023年2月21日周二 20:52写道：
>
> > congrats Sergey!
> >
> > On Tue, Feb 21, 2023 at 1:15 PM Matthias Pohl
> > wrote:
> >
> > > Congratulations, Sergey! Good job &
Congratulations, Sergey~
Best regards,
Weijie
Jing Ge 于2023年2月21日周二 20:52写道：
> congrats Sergey!
>
> On Tue, Feb 21, 2023 at 1:15 PM Matthias Pohl
> wrote:
>
> > Congratulations, Sergey! Good job & well-deserved! :)
> >
> > On Tue, Feb 21, 2023 at 1:03 PM yuxia
> wrote:
> >
> > >
congrats Sergey!
On Tue, Feb 21, 2023 at 1:15 PM Matthias Pohl
wrote:
> Congratulations, Sergey! Good job & well-deserved! :)
>
> On Tue, Feb 21, 2023 at 1:03 PM yuxia wrote:
>
> > Congratulations Sergey!
> >
> > Best regards,
> > Yuxia
> >
> > - 原始邮件 -
> > 发件人: "Martijn Visser"
> >
+ 1 for a new FLIP
It would be great if we could take this opportunity to go through all
current Flink SQL syntax and define a feasible classification in the FLIP.
In my opinion, the 4 categories, i.e. DDL, DML, DQL, DAL , used in Spark
doc [1] make sense.
We will then have a better big picture
Matthias Pohl created FLINK-31168:
-
Summary: JobManagerHAProcessFailureRecoveryITCase failed due to
job not being found
Key: FLINK-31168
URL: https://issues.apache.org/jira/browse/FLINK-31168
Hi Samrat,
I copied the thread as I wasn't subscribed previously.
I used the core ip address or core host names and they are identical
1. Flink 1.5.2
2. I don't get any exceptions, the logs at Trace level, no relevant errors.
I at5tched the jobmanager logs, the error log is empty
3.
Congratulations, Sergey! Good job & well-deserved! :)
On Tue, Feb 21, 2023 at 1:03 PM yuxia wrote:
> Congratulations Sergey!
>
> Best regards,
> Yuxia
>
> - 原始邮件 -
> 发件人: "Martijn Visser"
> 收件人: "dev"
> 发送时间: 星期二, 2023年 2 月 21日 下午 7:58:35
> 主题: Re: [ANNOUNCE] New Apache Flink
Thanks. I will create a FLIP to illustrate some details.
Best Regards,
Ran Tao
https://github.com/chucheng92
Jark Wu 于2023年2月21日周二 20:03写道：
> Thank you,
>
> I think this is worth a FLIP design doc to discuss the detailed syntax.
> Could you prepare a FLIP for that?
>
> Best,
> Jark
>
> On
Thank you,
I think this is worth a FLIP design doc to discuss the detailed syntax.
Could you prepare a FLIP for that?
Best,
Jark
On Tue, 21 Feb 2023 at 19:37, Ran Tao wrote:
> Hi, Jark. thanks. I have added a google doc.
>
>
>
Congratulations Sergey!
Best regards,
Yuxia
- 原始邮件 -
发件人: "Martijn Visser"
收件人: "dev"
发送时间: 星期二, 2023年 2 月 21日 下午 7:58:35
主题: Re: [ANNOUNCE] New Apache Flink Committer - Sergey Nuyanzin
Congrats Sergey, well deserved :)
On Tue, Feb 21, 2023 at 12:53 PM Benchao Li wrote:
>
Congrats Sergey, well deserved :)
On Tue, Feb 21, 2023 at 12:53 PM Benchao Li wrote:
> Congratulations Sergey!
>
> Timo Walther 于2023年2月21日周二 19:51写道：
>
> > Hi everyone,
> >
> > On behalf of the PMC, I'm very happy to announce Sergey Nuyanzin as a
> > new Flink Committer.
> >
> > Sergey
Congratulations Sergey!
Timo Walther 于2023年2月21日周二 19:51写道：
> Hi everyone,
>
> On behalf of the PMC, I'm very happy to announce Sergey Nuyanzin as a
> new Flink Committer.
>
> Sergey started contributing small improvements to the project in 2018.
> Over the past 1.5 years, he has become more
Hi everyone,
On behalf of the PMC, I'm very happy to announce Sergey Nuyanzin as a
new Flink Committer.
Sergey started contributing small improvements to the project in 2018.
Over the past 1.5 years, he has become more active and focused on adding
and reviewing changes to the Flink SQL
Hi, Jark. thanks. I have added a google doc.
https://docs.google.com/document/d/1hAiOfPx14VTBTOlpyxG7FA2mB1k5M31VnKYad2XpJ1I/edit?usp=sharing
Jark Wu 于2023年2月21日周二 19:27写道：
> Hi Ran,
>
> I think it’s always nice to support new syntax if it’s useful for the
> users.
> From my side, your syntax
Hi Ran,
I think it’s always nice to support new syntax if it’s useful for the users.
From my side, your syntax table is broken. Could you share it with a Google doc
or create a JIRA issue?
Best,
Jark
> 2023年2月21日 17:51，Ran Tao 写道：
>
> Hi guys. When I recently used flink sql to manage
Matthias Pohl created FLINK-31167:
-
Summary: Verify that no exclusions were erroneously added to the
japicmp plugin
Key: FLINK-31167
URL: https://issues.apache.org/jira/browse/FLINK-31167
Project:
jackylau created FLINK-31166:
Summary: array_contains element type error
Key: FLINK-31166
URL: https://issues.apache.org/jira/browse/FLINK-31166
Project: Flink
Issue Type: Bug
+1
On Tue, Feb 21, 2023 at 11:07 AM Martijn Visser
wrote:
>
> Hi all,
>
> +1 for this change. I see it as the responsibility of the community to make
> one more bugfix release available which for me is clear from the proposed
> text.
>
> Best regards,
>
> Martijn
>
> On Tue, Feb 21, 2023 at
Congrats Rui! Well done!!
-Max
On Tue, Feb 21, 2023 at 10:09 AM Roman Khachatryan wrote:
>
> Congratulations Rui!
>
> Regards,
> Roman
>
>
> On Mon, Feb 20, 2023 at 5:58 PM Anton Kalashnikov
> wrote:
>
> > Congrats Rui!
> >
> > --
> > Best regards,
> > Anton Kalashnikov
> >
> > On 20.02.23
-0 for a redesign. I might be the only one but I like the current
simple design. I find it quite elegant. Apache projects do not tend to
have fancy websites. That's ok. If you consider the AWS pages, they
are far from being modern or beautiful.
A redesign often is appealing but it can take a huge
Hi all,
+1 for this change. I see it as the responsibility of the community to make
one more bugfix release available which for me is clear from the proposed
text.
Best regards,
Martijn
On Tue, Feb 21, 2023 at 10:08 AM Danny Cranmer
wrote:
> Thanks all for the feedback.
>
> @Piotr/@Matthias
Hi guys. When I recently used flink sql to manage internal metadata
(catalog/databases/table/functions),
I found that many current flink sql statements do not support filtering or
some advanced syntax, however these abilities are very useful to end-users.
These are some statements I have
Congratulations Rui!
Regards,
Roman
On Mon, Feb 20, 2023 at 5:58 PM Anton Kalashnikov
wrote:
> Congrats Rui!
>
> --
> Best regards,
> Anton Kalashnikov
>
> On 20.02.23 17:53, Matthias Pohl wrote:
> > Congratulations, Rui :)
> >
> > On Mon, Feb 20, 2023 at 5:10 PM Jing Ge
> wrote:
> >
> >>
Congratulations Anton, well deserved!
Regards,
Roman
On Tue, Feb 21, 2023 at 9:34 AM Martijn Visser
wrote:
> Congratulations Anton!
>
> On Tue, Feb 21, 2023 at 8:08 AM Lincoln Lee
> wrote:
>
> > Congratulations, Anton!
> >
> > Best,
> > Lincoln Lee
> >
> >
> > Guowei Ma 于2023年2月21日周二
Thanks all for the feedback.
@Piotr/@Matthias my intention was to relax the support policy rather than
enforce patch releases to be performed immediately. I see pros and cons to
both, if we do not do the release immediately it may be dragged out, if we
enforce it, then it puts more burden on the
Hi Deepthi,
+1 for a redesign.
I like the idea of setting up a committee/team that can produce some mock
ups and create a FLIP where the community can elect the best look and feel.
I very much look forward to seeing the results!
Thanks,
Danny
On Tue, Feb 21, 2023 at 8:37 AM Jing Ge wrote:
P Rohan Kumar created FLINK-31165:
-
Summary: Over Agg: The window rank function without order by error
in top N query
Key: FLINK-31165
URL: https://issues.apache.org/jira/browse/FLINK-31165
Project:
Hi Deepthi,
Thanks for the feedback. Zeplin I mentioned is a UX/UI design software[1],
it is not Zeppelin.
It is great to hear that Amazon UX/UI designers would contribute. There was
a lack of front-end engineers in the past. Hopefully we could find enough
front-end contributors for this big
Congratulations Anton!
On Tue, Feb 21, 2023 at 8:08 AM Lincoln Lee wrote:
> Congratulations, Anton!
>
> Best,
> Lincoln Lee
>
>
> Guowei Ma 于2023年2月21日周二 15:05写道：
>
> > Congratulations, Anton!
> >
> > Best,
> > Guowei
> >
> >
> > On Tue, Feb 21, 2023 at 1:52 PM Shammon FY wrote:
> >
> > >
Congratulations Rui!
On Tue, Feb 21, 2023 at 8:07 AM Lincoln Lee wrote:
> Congratulations, Rui!
>
> Best,
> Lincoln Lee
>
>
> Guowei Ma 于2023年2月21日周二 15:03写道：
>
> > Congratulations, Rui!
> >
> > Best,
> > Guowei
> >
> >
> > On Tue, Feb 21, 2023 at 2:57 PM Wei Zhong
> wrote:
> >
> > >
Hi all,
I would +1 an overall redesign, but I would like to ask to wait until the
migration to Hugo has been completed [1]. That would make the themes and
technology between the project website and the documentation the same and
provide a foundation to continue for further improvements.
Best
Hi Italy,
`writeToSocket` supports passing the hostname , port and schema as
arguments.
I think you can pass the hostname of one of the core nodes in the flink job
you intend to view the message.
Have you tried that ?
Can you add more details ,
1. Which flink version are you using?
2. If you are
66 matches
Mail list logo
