Re: Connectin two jobs with socket over AWS EMR - How to define the ip?
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 getting some exception, can you add error logs.
3. Have you verified if your source is generating new records when you are
trying to view records in socket.
Bests,
Samrat
On Tue, Feb 21, 2023 at 1:27 PM Itay Sali wrote:
> Hi,
>
> I build a streaming pipeline and there are two jobs that I wish to connect
> with socket(later we plan to have kafka instead).
> The jobs submitted in AWS EMR cluster with this configuration
>
> {
> "Classification": "flink-conf",
> "Properties": {
> "JAVA_HOME": "/usr/lib/jvm/java-11-openjdk",
> "env.java.home": "/usr/lib/jvm/java-11-openjdk",
> "high-availability": "zookeeper",
> "high-availability.storageDir": "hdfs:///user/flink/recovery",
> "high-availability.zookeeper.path.root": "/flink",
> "high-availability.zookeeper.quorum": "%{hiera('hadoop::zk')}",
> "java.home": "/usr/lib/jvm/java-11-openjdk",
> "taskmanager.data.port": "35001",
> "taskmanager.numberOfTaskSlots": "2",
> "yarn.application-attempts": "10"
> }
> },
>
>
> I probably miss how to define the host when I use writeToSocket and
> socketToStream from my jobs.
> Is it configuration or one of the primary/core node ips. I have tried many
> options and non of the messages went through.
>
> Any help would be appreciated.
>
> Thanks,
> Itay Sali
>
Re: Proposal to improve the Apache Flink website
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 regards, Martijn [1] https://github.com/apache/flink-web/pull/597 On Tue, Feb 21, 2023 at 8:59 AM Shuo Cheng wrote: > Hey! > > +1 for the proposal, the first page of Flink is more like a tutorial > document for developers compared to the other top apache projects. Looking > forward to a more attractive Flink website. > > Best regards, > Shuo > > On Tue, Feb 21, 2023 at 8:13 AM Mohan, Deepthi > > wrote: > > > Hi, > > > > I am a product manager for Kinesis Data Analytics, AWS’s managed service > > for Apache Flink. I’m creating this thread to gauge community interest in > > redesigning the Flink website: https://flink.apache.org/. > > A few of our customers have provided feedback that the Apache Flink > > website looks dated. One customer claimed that the website looks > > “unwelcoming” and lacks useful graphics and colors. Another said it looks > > “like a wiki page thrown together by developers.” Customers also point > out > > other related Apache project websites: https://spark.apache.org/ and > > https://kafka.apache.org/ as having “modern” user design. Many were > > surprised to hear that Flink has been a top-5 Apache project for several > > years now. > > As https://flink.apache.org/ is likely the first page someone new to > > Flink encounters, it will be helpful to modernize the look and feel of > the > > website. Given the growing interest in Flink, we have an opportunity to > > make content and features visible and easily accessible to customers. I’d > > like to learn if this is an idea we should pursue. I can create a FLIP if > > there is interest. > > Thanks, > > Deepthi Mohan > > >
Re: [ANNOUNCE] New Apache Flink Committer - Rui Fan
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: > > > > > Congratulations, Rui! > > > > > > Best, > > > Wei > > > > > > > 2023年2月21日 下午1:52，Shammon FY 写道： > > > > > > > > Congratulations, Rui! > > > > > > > > > > > > Best, > > > > Shammon > > > > > > > > On Tue, Feb 21, 2023 at 1:40 PM Sergey Nuyanzin > > > > wrote: > > > > > > > >> Congratulations, Rui! > > > >> > > > >> On Tue, Feb 21, 2023 at 4:53 AM Weihua Hu > > > wrote: > > > >> > > > >>> Congratulations, Rui! > > > >>> > > > >>> Best, > > > >>> Weihua > > > >>> > > > >>> > > > >>> On Tue, Feb 21, 2023 at 11:28 AM Biao Geng > > > wrote: > > > >>> > > > Congrats, Rui! > > > Best, > > > Biao Geng > > > > > > weijie guo 于2023年2月21日周二 11:21写道： > > > > > > > Congrats, Rui! > > > > > > > > Best regards, > > > > > > > > Weijie > > > > > > > > > > > > Leonard Xu 于2023年2月21日周二 11:03写道： > > > > > > > >> Congratulations, Rui! > > > >> > > > >> Best, > > > >> Leonard > > > >> > > > >>> On Feb 21, 2023, at 9:50 AM, Matt Wang > wrote: > > > >>> > > > >>> Congrats Rui > > > >>> > > > >>> > > > >>> -- > > > >>> > > > >>> Best, > > > >>> Matt Wang > > > >>> > > > >>> > > > >>> Replied Message > > > >>> | From | yuxia | > > > >>> | Date | 02/21/2023 09:22 | > > > >>> | To | dev | > > > >>> | Subject | Re: [ANNOUNCE] New Apache Flink Committer - Rui > Fan | > > > >>> Congrats Rui > > > >>> > > > >>> Best regards, > > > >>> Yuxia > > > >>> > > > >>> - 原始邮件 - > > > >>> 发件人: "Samrat Deb" > > > >>> 收件人: "dev" > > > >>> 发送时间: 星期二, 2023年 2 月 21日 上午 1:09:25 > > > >>> 主题: Re: [ANNOUNCE] New Apache Flink Committer - Rui Fan > > > >>> > > > >>> Congrats Rui > > > >>> > > > >>> On Mon, 20 Feb 2023 at 10:28 PM, Anton Kalashnikov < > > > kaa@yandex.com > > > >> > > > >>> 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: > > > >>> > > > >>> Congrats Rui! > > > >>> > > > >>> On Mon, Feb 20, 2023 at 3:19 PM Piotr Nowojski < > > > >>> pnowoj...@apache.org > > > > > > > >>> wrote: > > > >>> > > > >>> Hi, everyone > > > >>> > > > >>> On behalf of the PMC, I'm very happy to announce Rui Fan as a > new > > > Flink > > > >>> Committer. > > > >>> > > > >>> Rui Fan has been active on a small scale since August 2019, and > > > ramped > > > >>> up > > > >>> his contributions in the 2nd half of 2021. He was mostly > involved > > > >>> in > > > >>> quite > > > >>> demanding performance related work around the network stack and > > > >>> checkpointing, like re-using TCP connections [1], and many > > > >> crucial > > > >>> improvements to the unaligned checkpoints. Among others: > > > >> FLIP-227: > > > >>> Support > > > >>> overdraft buffer [2], Merge small ChannelState file for > Unaligned > > > >>> Checkpoint [3], Timeout aligned to unaligned checkpoint barrier > > > >> in > > > the > > > >>> output buffers [4]. > > > >>> > > > >>> Please join me in congratulating Rui Fan for becoming a Flink > > > >>> Committer! > > > >>> > > > >>> Best, > > > >>> Piotr Nowojski (on behalf of the Flink PMC) > > > >>> > > > >>> [1] https://issues.apache.org/jira/browse/FLINK-22643 > > > >>> [2] > > > >>> > > > >>> > > > >>> > > > >>> > > > >> > > > > > > > > > > >>> > > > >> > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-227%3A+Support+overdraft+buffer > > > >>> [3] https://issues.apache.org/jira/browse/FLINK-26803 > > > >>> [4] https://issues.apache.org/jira/browse/FLINK-27251 > > > >>> > > > >>> > > > >> > > > >> > > > > > > > > > > >>> > > > >> > > > >> > > > >> -- > > > >> Best regards, > > > >> Sergey > > > >> > > > > > > > > >
Re: [ANNOUNCE] New Apache Flink Committer - Anton Kalashnikov
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, Anton! > > > > > > Best, > > > Shammon > > > > > > On Tue, Feb 21, 2023 at 1:41 PM Sergey Nuyanzin > > > wrote: > > > > > > > Congratulations, Anton! > > > > > > > > On Tue, Feb 21, 2023 at 4:53 AM Weihua Hu > > > wrote: > > > > > > > > > Congratulations, Anton! > > > > > > > > > > Best, > > > > > Weihua > > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 11:22 AM weijie guo < > > guoweijieres...@gmail.com > > > > > > > > > wrote: > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > Best regards, > > > > > > > > > > > > Weijie > > > > > > > > > > > > > > > > > > Leonard Xu 于2023年2月21日周二 11:02写道： > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > Best, > > > > > > > Leonard > > > > > > > > > > > > > > > > > > > > > > On Feb 21, 2023, at 10:02 AM, Rui Fan > > wrote: > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > Best, > > > > > > > > Rui Fan > > > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 9:23 AM yuxia < > > > luoyu...@alumni.sjtu.edu.cn > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > >> Congrats Anton! > > > > > > > >> > > > > > > > >> Best regards, > > > > > > > >> Yuxia > > > > > > > >> > > > > > > > >> - 原始邮件 - > > > > > > > >> 发件人: "Matthias Pohl" > > > > > > > >> 收件人: "dev" > > > > > > > >> 发送时间: 星期二, 2023年 2 月 21日 上午 12:52:40 > > > > > > > >> 主题: Re: [ANNOUNCE] New Apache Flink Committer - Anton > > > Kalashnikov > > > > > > > >> > > > > > > > >> Congratulations, Anton! :-) > > > > > > > >> > > > > > > > >> On Mon, Feb 20, 2023 at 5:09 PM Jing Ge > > > > > > > > > > > > > > > > >> wrote: > > > > > > > >> > > > > > > > >>> Congrats Anton! > > > > > > > >>> > > > > > > > >>> On Mon, Feb 20, 2023 at 5:02 PM Samrat Deb < > > > > decordea...@gmail.com> > > > > > > > >> wrote: > > > > > > > >>> > > > > > > > congratulations Anton! > > > > > > > > > > > > > > Bests, > > > > > > > Samrat > > > > > > > > > > > > > > On Mon, 20 Feb 2023 at 9:29 PM, John Roesler < > > > > vvcep...@apache.org > > > > > > > > > > > > > >>> wrote: > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > -John > > > > > > > > > > > > > > > > On Mon, Feb 20, 2023, at 08:18, Piotr Nowojski wrote: > > > > > > > >> Hi, everyone > > > > > > > >> > > > > > > > >> On behalf of the PMC, I'm very happy to announce Anton > > > > > Kalashnikov > > > > > > > >>> as a > > > > > > > > new > > > > > > > >> Flink Committer. > > > > > > > >> > > > > > > > >> Anton has been very active for almost two years already, > > > > > authored > > > > > > > >> and > > > > > > > >> reviewed many PRs over this time. He is active in the > > > Flink's > > > > > > > >>> runtime, > > > > > > > >> being the main author of improvements like Buffer > > Debloating > > > > > > > >>> (FLIP-183) > > > > > > > >> [1], solved many bugs and fixed many test instabilities, > > > > > generally > > > > > > > > speaking > > > > > > > >> helping with the maintenance of runtime components. > > > > > > > >> > > > > > > > >> Please join me in congratulating Anton Kalashnikov for > > > > becoming > > > > > a > > > > > > > >>> Flink > > > > > > > >> Committer! > > > > > > > >> > > > > > > > >> Best, > > > > > > > >> Piotr Nowojski (on behalf of the Flink PMC) > > > > > > > >> > > > > > > > >> [1] > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > >>> > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-183%3A+Dynamic+buffer+size+adjustment > > > > > > > > > > > > > > > > > > > > > > >>> > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Best regards, > > > > Sergey > > > > > > > > > >
Re: Proposal to improve the Apache Flink website
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 project. +1 looking forward to your proposal. Best regards, Jing [1] https://zeplin.io/ On Tue, Feb 21, 2023 at 8:59 AM Shuo Cheng wrote: > Hey! > > +1 for the proposal, the first page of Flink is more like a tutorial > document for developers compared to the other top apache projects. Looking > forward to a more attractive Flink website. > > Best regards, > Shuo > > On Tue, Feb 21, 2023 at 8:13 AM Mohan, Deepthi > > wrote: > > > Hi, > > > > I am a product manager for Kinesis Data Analytics, AWS’s managed service > > for Apache Flink. I’m creating this thread to gauge community interest in > > redesigning the Flink website: https://flink.apache.org/. > > A few of our customers have provided feedback that the Apache Flink > > website looks dated. One customer claimed that the website looks > > “unwelcoming” and lacks useful graphics and colors. Another said it looks > > “like a wiki page thrown together by developers.” Customers also point > out > > other related Apache project websites: https://spark.apache.org/ and > > https://kafka.apache.org/ as having “modern” user design. Many were > > surprised to hear that Flink has been a top-5 Apache project for several > > years now. > > As https://flink.apache.org/ is likely the first page someone new to > > Flink encounters, it will be helpful to modernize the look and feel of > the > > website. Given the growing interest in Flink, we have an opportunity to > > make content and features visible and easily accessible to customers. I’d > > like to learn if this is an idea we should pursue. I can create a FLIP if > > there is interest. > > Thanks, > > Deepthi Mohan > > >
[jira] [Created] (FLINK-31165) Over Agg: The window rank function without order by error in top N query
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: Flink
Issue Type: Bug
Components: Table SQL / API
Affects Versions: 1.16.0
Reporter: P Rohan Kumar
{code:java}
val env: StreamExecutionEnvironment =
StreamExecutionEnvironment.getExecutionEnvironment
val tableEnv = StreamTableEnvironment.create(env)
val td = TableDescriptor.forConnector("datagen").option("rows-per-second", "10")
.option("number-of-rows", "10")
.schema(Schema
.newBuilder()
.column("NAME", DataTypes.VARCHAR(2147483647))
.column("ROLLNO", DataTypes.DECIMAL(5, 0))
.column("DOB", DataTypes.DATE())
.column("CLASS", DataTypes.DECIMAL(2, 0))
.column("SUBJECT", DataTypes.VARCHAR(2147483647))
.build())
.build()
val table = tableEnv.from(td)
tableEnv.createTemporaryView("temp_table", table)
val newTable = tableEnv.sqlQuery("select temp_table.*,cast('2022-01-01' as
date) SRC_NO from temp_table")
tableEnv.createTemporaryView("temp_table2", newTable)
val newTable2 = tableEnv.sqlQuery("select * from (select
NAME,ROLLNO,row_number() over (partition by NAME ORDER BY SRC_NO) AS rownum
from temp_table2 a) where rownum <= 1")
tableEnv.toChangelogStream(newTable2).print()
env.execute()
{code}
I am getting the below error if I run the above code.
I have already provided an order by column.
If I change the order by column to some other column, such as "SUBJECT", then
the job runs fine.
{code:java}
Exception in thread "main" java.lang.RuntimeException: Error while applying
rule FlinkLogicalOverAggregateConverter(in:NONE,out:LOGICAL), args
[rel#245:LogicalWindow.NONE.any.None:
0.[NONE].[NONE](input=RelSubset#244,window#0=window(partition {0} rows between
UNBOUNDED PRECEDING and CURRENT ROW aggs [ROW_NUMBER()]))]
at
org.apache.calcite.plan.volcano.VolcanoRuleCall.onMatch(VolcanoRuleCall.java:256)
at
org.apache.calcite.plan.volcano.IterativeRuleDriver.drive(IterativeRuleDriver.java:58)
at
org.apache.calcite.plan.volcano.VolcanoPlanner.findBestExp(VolcanoPlanner.java:510)
at org.apache.calcite.tools.Programs$RuleSetProgram.run(Programs.java:312)
at
org.apache.flink.table.planner.plan.optimize.program.FlinkVolcanoProgram.optimize(FlinkVolcanoProgram.scala:62)
at
org.apache.flink.table.planner.plan.optimize.program.FlinkChainedProgram.$anonfun$optimize$1(FlinkChainedProgram.scala:59)
at
scala.collection.TraversableOnce$folder$1$.apply(TraversableOnce.scala:187)
at
scala.collection.TraversableOnce$folder$1$.apply(TraversableOnce.scala:185)
at scala.collection.Iterator.foreach(Iterator.scala:943)
at scala.collection.Iterator.foreach$(Iterator.scala:943)
at scala.collection.AbstractIterator.foreach(Iterator.scala:1431)
at scala.collection.IterableLike.foreach(IterableLike.scala:74)
at scala.collection.IterableLike.foreach$(IterableLike.scala:73)
at scala.collection.AbstractIterable.foreach(Iterable.scala:56)
at scala.collection.TraversableOnce.foldLeft(TraversableOnce.scala:189)
at scala.collection.TraversableOnce.foldLeft$(TraversableOnce.scala:184)
at scala.collection.AbstractTraversable.foldLeft(Traversable.scala:108)
at
org.apache.flink.table.planner.plan.optimize.program.FlinkChainedProgram.optimize(FlinkChainedProgram.scala:55)
at
org.apache.flink.table.planner.plan.optimize.StreamCommonSubGraphBasedOptimizer.optimizeTree(StreamCommonSubGraphBasedOptimizer.scala:176)
at
org.apache.flink.table.planner.plan.optimize.StreamCommonSubGraphBasedOptimizer.doOptimize(StreamCommonSubGraphBasedOptimizer.scala:83)
at
org.apache.flink.table.planner.plan.optimize.CommonSubGraphBasedOptimizer.optimize(CommonSubGraphBasedOptimizer.scala:87)
at
org.apache.flink.table.planner.delegation.PlannerBase.optimize(PlannerBase.scala:315)
at
org.apache.flink.table.planner.delegation.PlannerBase.translate(PlannerBase.scala:195)
at
org.apache.flink.table.api.bridge.internal.AbstractStreamTableEnvironmentImpl.toStreamInternal(AbstractStreamTableEnvironmentImpl.java:224)
at
org.apache.flink.table.api.bridge.internal.AbstractStreamTableEnvironmentImpl.toStreamInternal(AbstractStreamTableEnvironmentImpl.java:219)
at
org.apache.flink.table.api.bridge.scala.internal.StreamTableEnvironmentImpl.toChangelogStream(StreamTableEnvironmentImpl.scala:160)
at org.example.OverAggregateBug$.main(OverAggregateBug.scala:39)
at org.example.OverAggregateBug.main(OverAggregateBug.scala)
Caused by: org.apache.flink.table.api.ValidationException: Over Agg: The window
rank function without order by. please re-check the over window statement.
at
org.apache.flink.table.planner.plan.nodes.logical.FlinkLogicalOverAggregateConverter.$anonfu
Re: Proposal to improve the Apache Flink website
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: > 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 project. > > +1 looking forward to your proposal. > > Best regards, > Jing > > [1] https://zeplin.io/ > > On Tue, Feb 21, 2023 at 8:59 AM Shuo Cheng wrote: > > > Hey! > > > > +1 for the proposal, the first page of Flink is more like a tutorial > > document for developers compared to the other top apache projects. > Looking > > forward to a more attractive Flink website. > > > > Best regards, > > Shuo > > > > On Tue, Feb 21, 2023 at 8:13 AM Mohan, Deepthi > > > > > wrote: > > > > > Hi, > > > > > > I am a product manager for Kinesis Data Analytics, AWS’s managed > service > > > for Apache Flink. I’m creating this thread to gauge community interest > in > > > redesigning the Flink website: https://flink.apache.org/. > > > A few of our customers have provided feedback that the Apache Flink > > > website looks dated. One customer claimed that the website looks > > > “unwelcoming” and lacks useful graphics and colors. Another said it > looks > > > “like a wiki page thrown together by developers.” Customers also point > > out > > > other related Apache project websites: https://spark.apache.org/ and > > > https://kafka.apache.org/ as having “modern” user design. Many were > > > surprised to hear that Flink has been a top-5 Apache project for > several > > > years now. > > > As https://flink.apache.org/ is likely the first page someone new to > > > Flink encounters, it will be helpful to modernize the look and feel of > > the > > > website. Given the growing interest in Flink, we have an opportunity to > > > make content and features visible and easily accessible to customers. > I’d > > > like to learn if this is an idea we should pursue. I can create a FLIP > if > > > there is interest. > > > Thanks, > > > Deepthi Mohan > > > > > >
Re: [DISCUSS] Flink minor version support policy for old releases
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 release manager. A compromise could be for the release manager to start the discussion thread and volunteer to be release manager if they have capacity. We can update the release process [1] to include this final step. In summary I am proposing the following: - Support policy += "Upon release of a new Flink minor version, the community will perform one final bugfix release for resolved critical/blocker issues in the Flink version losing support." - Release process += Add a step to start the discussion thread for the final 1.n-2 patch version, IF there are resolved critical/blocking issues. To clarify, major/minor bug fixes are out of scope of this policy. If we are aligned I will start a vote thread. Thanks, Danny [1] https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release On Mon, Feb 20, 2023 at 3:47 PM Piotr Nowojski wrote: > +1 for the proposal, it makes sense to me. > > Re Matthias, I think ideally it would be better for the minor release > manager to do the final bug fix, so that we have a clear person that's > responsible for that. Otherwise I have some fear that we would forget about > doing that. But I'm fine trying it out the way Matthias proposed, maybe I'm > worrying over nothing. > > Best, > Piotrek > > pon., 20 lut 2023 o 12:34 Matthias Pohl > napisał(a): > > > +1 > > Thanks for picking it up, Danny. Your change makes sense. One question, > > though: The phrase makes it sound like we're doing it mandatorily. With > > this in mind, I would see the responsibility on the minor-release release > > managers' side (in your example 1.17). I would prefer to have it > decoupled > > to reduce the amount of responsibilities on the minor-release release > > manager's side. Therefore, I'd propose a slightly different phrasing: > > "Upon release of a new Flink minor version, the community encourages to > > perform a final bugfix release for resolved critical/blocker issues in > the > > Flink version losing support." > > > > This phrasing implies that the final flush-out patch release is still > > decoupled from the minor release. > > > > On Mon, Feb 20, 2023 at 9:02 AM weijie guo > > wrote: > > > > > Thanks Danny for the proposal~ > > > > > > +1 for this. In particular, we still have some users using relatively > > early > > > versions of flink. > > > > > > Best regards, > > > > > > Weijie > > > > > > > > > yuxia 于2023年2月20日周一 14:51写道： > > > > > > > +1 > > > > Thanks for the proposal. > > > > > > > > Best regards, > > > > Yuxia > > > > > > > > - 原始邮件 - > > > > 发件人: "Weihua Hu" > > > > 收件人: "dev" > > > > 发送时间: 星期一, 2023年 2 月 20日 下午 2:36:08 > > > > 主题: Re: [DISCUSS] Flink minor version support policy for old releases > > > > > > > > +1 > > > > > > > > Thanks for the proposal, this is valuable for stability. > > > > > > > > Best, > > > > Weihua > > > > > > > > > > > > On Mon, Feb 20, 2023 at 10:52 AM Dong Lin > wrote: > > > > > > > > > This makes a lot of sense. Thanks Danny for the proposal! > > > > > > > > > > +1 > > > > > > > > > > On Sat, Feb 18, 2023 at 12:52 AM Danny Cranmer < > > > dannycran...@apache.org> > > > > > wrote: > > > > > > > > > > > Hello all, > > > > > > > > > > > > As proposed by Matthias in a separate thread [1], I would like to > > > > start a > > > > > > discussion on changing the policy wording to include the release > of > > > bug > > > > > > fixes during their support window. Our current policy [2] is to > > only > > > > > > support the latest two minor versions: " If 1.17.x is the current > > > > > release, > > > > > > 1.16.y is the previous minor supported release. Both versions > will > > > > > receive > > > > > > bugfixes for critical issues.". However there may be bug fixes > that > > > > have > > > > > > been resolved but not released during their support window. > > Consider > > > > this > > > > > > example: > > > > > > 1. Current Flink versions are 1.15.3 and 1.16.1 > > > > > > 2. We fix bugs for 1.15.3 > > > > > > 3. 1.17.0 is released > > > > > > 4. The 1.15 bug fixes will now not be released unless we get an > > > > exception > > > > > > > > > > > > The current process is subject to race conditions between > releases. > > > > > Should > > > > > > we upgrade the policy to allow bugfix releases to support issues > > that > > > > > were > > > > > > resolved during their support window. I propose we update the > > policy > > > to > > > > > > include: > > > > > > > > > > > > "Upon release of a new Flink minor version, the community will > > > perform > > > > > one > > > > > > final bugfix release for resolved critical/blocker issues in the > > > Flink > > > > > > version losing support." > > > > > > > > > > > > Let's discuss. > > > > > > > > >
Re: [ANNOUNCE] New Apache Flink Committer - Anton Kalashnikov
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日周二 15:05写道： > > > > > Congratulations, Anton! > > > > > > Best, > > > Guowei > > > > > > > > > On Tue, Feb 21, 2023 at 1:52 PM Shammon FY wrote: > > > > > > > Congratulations, Anton! > > > > > > > > Best, > > > > Shammon > > > > > > > > On Tue, Feb 21, 2023 at 1:41 PM Sergey Nuyanzin > > > > > wrote: > > > > > > > > > Congratulations, Anton! > > > > > > > > > > On Tue, Feb 21, 2023 at 4:53 AM Weihua Hu > > > > wrote: > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > Best, > > > > > > Weihua > > > > > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 11:22 AM weijie guo < > > > guoweijieres...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > Weijie > > > > > > > > > > > > > > > > > > > > > Leonard Xu 于2023年2月21日周二 11:02写道： > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > Best, > > > > > > > > Leonard > > > > > > > > > > > > > > > > > > > > > > > > > On Feb 21, 2023, at 10:02 AM, Rui Fan > > > wrote: > > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > Rui Fan > > > > > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 9:23 AM yuxia < > > > > luoyu...@alumni.sjtu.edu.cn > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > >> Congrats Anton! > > > > > > > > >> > > > > > > > > >> Best regards, > > > > > > > > >> Yuxia > > > > > > > > >> > > > > > > > > >> - 原始邮件 - > > > > > > > > >> 发件人: "Matthias Pohl" > > > > > > > > >> 收件人: "dev" > > > > > > > > >> 发送时间: 星期二, 2023年 2 月 21日 上午 12:52:40 > > > > > > > > >> 主题: Re: [ANNOUNCE] New Apache Flink Committer - Anton > > > > Kalashnikov > > > > > > > > >> > > > > > > > > >> Congratulations, Anton! :-) > > > > > > > > >> > > > > > > > > >> On Mon, Feb 20, 2023 at 5:09 PM Jing Ge > > > > > > > > > > > > > > > > > > > >> wrote: > > > > > > > > >> > > > > > > > > >>> Congrats Anton! > > > > > > > > >>> > > > > > > > > >>> On Mon, Feb 20, 2023 at 5:02 PM Samrat Deb < > > > > > decordea...@gmail.com> > > > > > > > > >> wrote: > > > > > > > > >>> > > > > > > > > congratulations Anton! > > > > > > > > > > > > > > > > Bests, > > > > > > > > Samrat > > > > > > > > > > > > > > > > On Mon, 20 Feb 2023 at 9:29 PM, John Roesler < > > > > > vvcep...@apache.org > > > > > > > > > > > > > > > >>> wrote: > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > -John > > > > > > > > > > > > > > > > > > On Mon, Feb 20, 2023, at 08:18, Piotr Nowojski wrote: > > > > > > > > >> Hi, everyone > > > > > > > > >> > > > > > > > > >> On behalf of the PMC, I'm very happy to announce Anton > > > > > > Kalashnikov > > > > > > > > >>> as a > > > > > > > > > new > > > > > > > > >> Flink Committer. > > > > > > > > >> > > > > > > > > >> Anton has been very active for almost two years > already, > > > > > > authored > > > > > > > > >> and > > > > > > > > >> reviewed many PRs over this time. He is active in the > > > > Flink's > > > > > > > > >>> runtime, > > > > > > > > >> being the main author of improvements like Buffer > > > Debloating > > > > > > > > >>> (FLIP-183) > > > > > > > > >> [1], solved many bugs and fixed many test > instabilities, > > > > > > generally > > > > > > > > > speaking > > > > > > > > >> helping with the maintenance of runtime components. > > > > > > > > >> > > > > > > > > >> Please join me in congratulating Anton Kalashnikov for > > > > > becoming > > > > > > a > > > > > > > > >>> Flink > > > > > > > > >> Committer! > > > > > > > > >> > > > > > > > > >> Best, > > > > > > > > >> Piotr Nowojski (on behalf of the Flink PMC) > > > > > > > > >> > > > > > > > > >> [1] > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > >>> > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-183%3A+Dynamic+buffer+size+adjustment > > > > > > > > > > > > > > > > > > > > > > > > > >>> > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Best regards, > > > > > Sergey > > > > > > > > > > > > > > >
Re: [ANNOUNCE] New Apache Flink Committer - Rui Fan
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: > > > >> Congrats Rui! > >> > >> On Mon, Feb 20, 2023 at 3:19 PM Piotr Nowojski > >> wrote: > >> > >>> Hi, everyone > >>> > >>> On behalf of the PMC, I'm very happy to announce Rui Fan as a new Flink > >>> Committer. > >>> > >>> Rui Fan has been active on a small scale since August 2019, and ramped > up > >>> his contributions in the 2nd half of 2021. He was mostly involved in > >> quite > >>> demanding performance related work around the network stack and > >>> checkpointing, like re-using TCP connections [1], and many crucial > >>> improvements to the unaligned checkpoints. Among others: FLIP-227: > >> Support > >>> overdraft buffer [2], Merge small ChannelState file for Unaligned > >>> Checkpoint [3], Timeout aligned to unaligned checkpoint barrier in the > >>> output buffers [4]. > >>> > >>> Please join me in congratulating Rui Fan for becoming a Flink > Committer! > >>> > >>> Best, > >>> Piotr Nowojski (on behalf of the Flink PMC) > >>> > >>> [1] https://issues.apache.org/jira/browse/FLINK-22643 > >>> [2] > >>> > >>> > >> > https://cwiki.apache.org/confluence/display/FLINK/FLIP-227%3A+Support+overdraft+buffer > >>> [3] https://issues.apache.org/jira/browse/FLINK-26803 > >>> [4] https://issues.apache.org/jira/browse/FLINK-27251 > >>> >
[DISCUSS] Proposal to improve Auxiliary Sql Statements
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 collected so far, which are supported on other big data engines, such as spark, hive or presto. I wonder if we can support these abilities? In addition, the subject of this email is named 'Auxiliary Statements' mainly because the alignment of these statements will not have much impact on the core SQL runtime. Support or Not With Advanced Syntax Or Not (in/from or like) show create table Yes Yes show tables Yes Yes show columns Yes Yes show catalogs Yes without filter show databases Yes without filter show functions Yes without filter show views Yes without filter show modules Yes without filter show jars Yes without filter show jobs Yes without filter We can see current flink many sql statements only support showing with full datas, without 'FROM/IN' or 'LIKE' filter clause. Support or Not describe database No describe table Yes describe function No describe query No current flink only supports describing tables. Also, please let me know if there is a mistake. Looking forward to your reply. Best Regards, Ran Tao https://github.com/chucheng92
Re: [DISCUSS] Flink minor version support policy for old releases
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 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 release manager. A compromise > could be for the release manager to start the discussion thread and > volunteer to be release manager if they have capacity. We can update the > release process [1] to include this final step. > > In summary I am proposing the following: > - Support policy += "Upon release of a new Flink minor version, the > community will perform one final bugfix release for resolved > critical/blocker issues in the Flink version losing support." > - Release process += Add a step to start the discussion thread for the > final 1.n-2 patch version, IF there are resolved critical/blocking issues. > > To clarify, major/minor bug fixes are out of scope of this policy. > > If we are aligned I will start a vote thread. > > Thanks, > Danny > > [1] > https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release > > > > On Mon, Feb 20, 2023 at 3:47 PM Piotr Nowojski > wrote: > > > +1 for the proposal, it makes sense to me. > > > > Re Matthias, I think ideally it would be better for the minor release > > manager to do the final bug fix, so that we have a clear person that's > > responsible for that. Otherwise I have some fear that we would forget > about > > doing that. But I'm fine trying it out the way Matthias proposed, maybe > I'm > > worrying over nothing. > > > > Best, > > Piotrek > > > > pon., 20 lut 2023 o 12:34 Matthias Pohl > > napisał(a): > > > > > +1 > > > Thanks for picking it up, Danny. Your change makes sense. One question, > > > though: The phrase makes it sound like we're doing it mandatorily. With > > > this in mind, I would see the responsibility on the minor-release > release > > > managers' side (in your example 1.17). I would prefer to have it > > decoupled > > > to reduce the amount of responsibilities on the minor-release release > > > manager's side. Therefore, I'd propose a slightly different phrasing: > > > "Upon release of a new Flink minor version, the community encourages to > > > perform a final bugfix release for resolved critical/blocker issues in > > the > > > Flink version losing support." > > > > > > This phrasing implies that the final flush-out patch release is still > > > decoupled from the minor release. > > > > > > On Mon, Feb 20, 2023 at 9:02 AM weijie guo > > > wrote: > > > > > > > Thanks Danny for the proposal~ > > > > > > > > +1 for this. In particular, we still have some users using relatively > > > early > > > > versions of flink. > > > > > > > > Best regards, > > > > > > > > Weijie > > > > > > > > > > > > yuxia 于2023年2月20日周一 14:51写道： > > > > > > > > > +1 > > > > > Thanks for the proposal. > > > > > > > > > > Best regards, > > > > > Yuxia > > > > > > > > > > - 原始邮件 - > > > > > 发件人: "Weihua Hu" > > > > > 收件人: "dev" > > > > > 发送时间: 星期一, 2023年 2 月 20日 下午 2:36:08 > > > > > 主题: Re: [DISCUSS] Flink minor version support policy for old > releases > > > > > > > > > > +1 > > > > > > > > > > Thanks for the proposal, this is valuable for stability. > > > > > > > > > > Best, > > > > > Weihua > > > > > > > > > > > > > > > On Mon, Feb 20, 2023 at 10:52 AM Dong Lin > > wrote: > > > > > > > > > > > This makes a lot of sense. Thanks Danny for the proposal! > > > > > > > > > > > > +1 > > > > > > > > > > > > On Sat, Feb 18, 2023 at 12:52 AM Danny Cranmer < > > > > dannycran...@apache.org> > > > > > > wrote: > > > > > > > > > > > > > Hello all, > > > > > > > > > > > > > > As proposed by Matthias in a separate thread [1], I would like > to > > > > > start a > > > > > > > discussion on changing the policy wording to include the > release > > of > > > > bug > > > > > > > fixes during their support window. Our current policy [2] is to > > > only > > > > > > > support the latest two minor versions: " If 1.17.x is the > current > > > > > > release, > > > > > > > 1.16.y is the previous minor supported release. Both versions > > will > > > > > > receive > > > > > > > bugfixes for critical issues.". However there may be bug fixes > > that > > > > > have > > > > > > > been resolved but not released during their support window. > > > Consider > > > > > this > > > > > > > example: > > > > > > > 1. Current Flink versions are 1.15.3 and 1.16.1 > > > > > > > 2. We fix bugs for 1.15.3 > > > > > > > 3. 1.17.0 is released > > > > > > > 4. The 1.15 bug fixes will now not be released unless we get an > > > > > exception > > > > > > > > > > > > > > The current process is subject to race conditions between > > releases. > >
Re: Proposal to improve the Apache Flink website
-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 amount of time to get it right. This can mean the project is unable to focus on the main target of delivering great software and documentation. Some concerns: 1. Content regressions (content not being displayed properly, content and graphics not fitting anymore, code formatting breaking) 2. Higher entry barrier for committing (tooling / formatting becomes complicated) 3. Lack of focus on the content which needs work too (e.g. outdated information, lack of documentation of features) That said, I would support a redesign if we prevent regressions and build on standard tooling and best practices. I'm just not convinced (yet) that the pros outweigh the cons. -Max On Tue, Feb 21, 2023 at 9:57 AM Danny Cranmer wrote: > > 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: > > > 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 project. > > > > +1 looking forward to your proposal. > > > > Best regards, > > Jing > > > > [1] https://zeplin.io/ > > > > On Tue, Feb 21, 2023 at 8:59 AM Shuo Cheng wrote: > > > > > Hey! > > > > > > +1 for the proposal, the first page of Flink is more like a tutorial > > > document for developers compared to the other top apache projects. > > Looking > > > forward to a more attractive Flink website. > > > > > > Best regards, > > > Shuo > > > > > > On Tue, Feb 21, 2023 at 8:13 AM Mohan, Deepthi > > > > > > > > wrote: > > > > > > > Hi, > > > > > > > > I am a product manager for Kinesis Data Analytics, AWS’s managed > > service > > > > for Apache Flink. I’m creating this thread to gauge community interest > > in > > > > redesigning the Flink website: https://flink.apache.org/. > > > > A few of our customers have provided feedback that the Apache Flink > > > > website looks dated. One customer claimed that the website looks > > > > “unwelcoming” and lacks useful graphics and colors. Another said it > > looks > > > > “like a wiki page thrown together by developers.” Customers also point > > > out > > > > other related Apache project websites: https://spark.apache.org/ and > > > > https://kafka.apache.org/ as having “modern” user design. Many were > > > > surprised to hear that Flink has been a top-5 Apache project for > > several > > > > years now. > > > > As https://flink.apache.org/ is likely the first page someone new to > > > > Flink encounters, it will be helpful to modernize the look and feel of > > > the > > > > website. Given the growing interest in Flink, we have an opportunity to > > > > make content and features visible and easily accessible to customers. > > I’d > > > > like to learn if this is an idea we should pursue. I can create a FLIP > > if > > > > there is interest. > > > > Thanks, > > > > Deepthi Mohan > > > > > > > > >
Re: [ANNOUNCE] New Apache Flink Committer - Rui Fan
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 17:53, Matthias Pohl wrote: > > > Congratulations, Rui :) > > > > > > On Mon, Feb 20, 2023 at 5:10 PM Jing Ge > > wrote: > > > > > >> Congrats Rui! > > >> > > >> On Mon, Feb 20, 2023 at 3:19 PM Piotr Nowojski > > >> wrote: > > >> > > >>> Hi, everyone > > >>> > > >>> On behalf of the PMC, I'm very happy to announce Rui Fan as a new Flink > > >>> Committer. > > >>> > > >>> Rui Fan has been active on a small scale since August 2019, and ramped > > up > > >>> his contributions in the 2nd half of 2021. He was mostly involved in > > >> quite > > >>> demanding performance related work around the network stack and > > >>> checkpointing, like re-using TCP connections [1], and many crucial > > >>> improvements to the unaligned checkpoints. Among others: FLIP-227: > > >> Support > > >>> overdraft buffer [2], Merge small ChannelState file for Unaligned > > >>> Checkpoint [3], Timeout aligned to unaligned checkpoint barrier in the > > >>> output buffers [4]. > > >>> > > >>> Please join me in congratulating Rui Fan for becoming a Flink > > Committer! > > >>> > > >>> Best, > > >>> Piotr Nowojski (on behalf of the Flink PMC) > > >>> > > >>> [1] https://issues.apache.org/jira/browse/FLINK-22643 > > >>> [2] > > >>> > > >>> > > >> > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-227%3A+Support+overdraft+buffer > > >>> [3] https://issues.apache.org/jira/browse/FLINK-26803 > > >>> [4] https://issues.apache.org/jira/browse/FLINK-27251 > > >>> > >
Re: [DISCUSS] Flink minor version support policy for old releases
+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 10:08 AM Danny Cranmer > wrote: > > > 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 release manager. A compromise > > could be for the release manager to start the discussion thread and > > volunteer to be release manager if they have capacity. We can update the > > release process [1] to include this final step. > > > > In summary I am proposing the following: > > - Support policy += "Upon release of a new Flink minor version, the > > community will perform one final bugfix release for resolved > > critical/blocker issues in the Flink version losing support." > > - Release process += Add a step to start the discussion thread for the > > final 1.n-2 patch version, IF there are resolved critical/blocking issues. > > > > To clarify, major/minor bug fixes are out of scope of this policy. > > > > If we are aligned I will start a vote thread. > > > > Thanks, > > Danny > > > > [1] > > https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release > > > > > > > > On Mon, Feb 20, 2023 at 3:47 PM Piotr Nowojski > > wrote: > > > > > +1 for the proposal, it makes sense to me. > > > > > > Re Matthias, I think ideally it would be better for the minor release > > > manager to do the final bug fix, so that we have a clear person that's > > > responsible for that. Otherwise I have some fear that we would forget > > about > > > doing that. But I'm fine trying it out the way Matthias proposed, maybe > > I'm > > > worrying over nothing. > > > > > > Best, > > > Piotrek > > > > > > pon., 20 lut 2023 o 12:34 Matthias Pohl > > > napisał(a): > > > > > > > +1 > > > > Thanks for picking it up, Danny. Your change makes sense. One question, > > > > though: The phrase makes it sound like we're doing it mandatorily. With > > > > this in mind, I would see the responsibility on the minor-release > > release > > > > managers' side (in your example 1.17). I would prefer to have it > > > decoupled > > > > to reduce the amount of responsibilities on the minor-release release > > > > manager's side. Therefore, I'd propose a slightly different phrasing: > > > > "Upon release of a new Flink minor version, the community encourages to > > > > perform a final bugfix release for resolved critical/blocker issues in > > > the > > > > Flink version losing support." > > > > > > > > This phrasing implies that the final flush-out patch release is still > > > > decoupled from the minor release. > > > > > > > > On Mon, Feb 20, 2023 at 9:02 AM weijie guo > > > > wrote: > > > > > > > > > Thanks Danny for the proposal~ > > > > > > > > > > +1 for this. In particular, we still have some users using relatively > > > > early > > > > > versions of flink. > > > > > > > > > > Best regards, > > > > > > > > > > Weijie > > > > > > > > > > > > > > > yuxia 于2023年2月20日周一 14:51写道： > > > > > > > > > > > +1 > > > > > > Thanks for the proposal. > > > > > > > > > > > > Best regards, > > > > > > Yuxia > > > > > > > > > > > > - 原始邮件 - > > > > > > 发件人: "Weihua Hu" > > > > > > 收件人: "dev" > > > > > > 发送时间: 星期一, 2023年 2 月 20日 下午 2:36:08 > > > > > > 主题: Re: [DISCUSS] Flink minor version support policy for old > > releases > > > > > > > > > > > > +1 > > > > > > > > > > > > Thanks for the proposal, this is valuable for stability. > > > > > > > > > > > > Best, > > > > > > Weihua > > > > > > > > > > > > > > > > > > On Mon, Feb 20, 2023 at 10:52 AM Dong Lin > > > wrote: > > > > > > > > > > > > > This makes a lot of sense. Thanks Danny for the proposal! > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > On Sat, Feb 18, 2023 at 12:52 AM Danny Cranmer < > > > > > dannycran...@apache.org> > > > > > > > wrote: > > > > > > > > > > > > > > > Hello all, > > > > > > > > > > > > > > > > As proposed by Matthias in a separate thread [1], I would like > > to > > > > > > start a > > > > > > > > discussion on changing the policy wording to include the > > release > > > of > > > > > bug > > > > > > > > fixes during their support window. Our current policy [2] is to > > > > only > > > > > > > > support the latest two minor versions: " If 1.17.x is the > > current > > > > > > > release, > > > > > > > > 1.16.y is the previous minor supported release. Both versions > > > will > > > > > > > receive > > > > > > > > bugfixes for critical issues.". However there may be bug fixes > > > that > > > > > > have > > > > > > > > been resolved but not released during their support window. > > > > Consider > > > > > > this > > > >
[jira] [Created] (FLINK-31166) array_contains element type error
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 Components: Table SQL / Planner Affects Versions: 1.18.0 Reporter: jackylau Fix For: 1.18.0 Attachments: image-2023-02-21-18-37-45-202.png, image-2023-02-21-18-38-04-226.png, image-2023-02-21-18-41-19-385.png, image-2023-02-21-18-41-27-757.png !image-2023-02-21-18-41-27-757.png! !image-2023-02-21-18-41-19-385.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-31167) Verify that no exclusions were erroneously added to the japicmp plugin
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: Flink
Issue Type: Sub-task
Reporter: Matthias Pohl
Verify that no exclusions were erroneously added to the japicmp plugin that
break compatibility guarantees. Check the exclusions for the
japicmp-maven-plugin in the root pom (see
[apache/flink:pom.xml:2175ff|https://github.com/apache/flink/blob/3856c49af77601cf7943a5072d8c932279ce46b4/pom.xml#L2175]
for exclusions that:
* For minor releases: break source compatibility for {{@Public}} APIs
* For patch releases: break source/binary compatibility for
{{@Public}}/{{@PublicEvolving}} APIs
Any such exclusion must be properly justified, in advance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements
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 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 collected so far, which are supported on > other big data engines, such as spark, hive or presto. I wonder if we can > support these abilities? > > In addition, the subject of this email is named 'Auxiliary Statements' > mainly because the alignment of these statements will not have much impact > on the core SQL runtime. > > Support or Not > > With Advanced Syntax Or Not (in/from or like) > > show create table > > Yes > > Yes > > show tables > > Yes > > Yes > > show columns > > Yes > > Yes > > show catalogs > > Yes > > without filter > > show databases > > Yes > > without filter > > show functions > > Yes > > without filter > > show views > > Yes > > without filter > > show modules > > Yes > > without filter > > show jars > > Yes > > without filter > > show jobs > > Yes > > without filter > > We can see current flink many sql statements only support showing with full > datas, without 'FROM/IN' or 'LIKE' filter clause. > > Support or Not > > describe database > > No > > describe table > > Yes > > describe function > > No > > describe query > > No > > current flink only supports describing tables. > > Also, please let me know if there is a mistake. Looking forward to your > reply. > > > Best Regards, > Ran Tao > https://github.com/chucheng92
Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements
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 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 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 collected so far, which are supported on > > other big data engines, such as spark, hive or presto. I wonder if we can > > support these abilities? > > > > In addition, the subject of this email is named 'Auxiliary Statements' > > mainly because the alignment of these statements will not have much > impact > > on the core SQL runtime. > > > > Support or Not > > > > With Advanced Syntax Or Not (in/from or like) > > > > show create table > > > > Yes > > > > Yes > > > > show tables > > > > Yes > > > > Yes > > > > show columns > > > > Yes > > > > Yes > > > > show catalogs > > > > Yes > > > > without filter > > > > show databases > > > > Yes > > > > without filter > > > > show functions > > > > Yes > > > > without filter > > > > show views > > > > Yes > > > > without filter > > > > show modules > > > > Yes > > > > without filter > > > > show jars > > > > Yes > > > > without filter > > > > show jobs > > > > Yes > > > > without filter > > > > We can see current flink many sql statements only support showing with > full > > datas, without 'FROM/IN' or 'LIKE' filter clause. > > > > Support or Not > > > > describe database > > > > No > > > > describe table > > > > Yes > > > > describe function > > > > No > > > > describe query > > > > No > > > > current flink only supports describing tables. > > > > Also, please let me know if there is a mistake. Looking forward to your > > reply. > > > > > > Best Regards, > > Ran Tao > > https://github.com/chucheng92 > >
[ANNOUNCE] New Apache Flink Committer - Sergey Nuyanzin
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 ecosystem. Currently, he is upgrading Flink's SQL engine to the latest Apache Calcite version [1][2][3] and helps in updating other project-wide dependencies as well. Please join me in congratulating Sergey Nuyanzin for becoming a Flink Committer! Best, Timo Walther (on behalf of the Flink PMC) [1] https://issues.apache.org/jira/browse/FLINK-29932 [2] https://issues.apache.org/jira/browse/FLINK-21239 [3] https://issues.apache.org/jira/browse/FLINK-20873
Re: [ANNOUNCE] New Apache Flink Committer - Sergey Nuyanzin
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 active and focused on adding > and reviewing changes to the Flink SQL ecosystem. > > Currently, he is upgrading Flink's SQL engine to the latest Apache > Calcite version [1][2][3] and helps in updating other project-wide > dependencies as well. > > Please join me in congratulating Sergey Nuyanzin for becoming a Flink > Committer! > > Best, > Timo Walther (on behalf of the Flink PMC) > > [1] https://issues.apache.org/jira/browse/FLINK-29932 > [2] https://issues.apache.org/jira/browse/FLINK-21239 > [3] https://issues.apache.org/jira/browse/FLINK-20873 > -- Best, Benchao Li
Re: [ANNOUNCE] New Apache Flink Committer - Sergey Nuyanzin
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 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 ecosystem. > > > > Currently, he is upgrading Flink's SQL engine to the latest Apache > > Calcite version [1][2][3] and helps in updating other project-wide > > dependencies as well. > > > > Please join me in congratulating Sergey Nuyanzin for becoming a Flink > > Committer! > > > > Best, > > Timo Walther (on behalf of the Flink PMC) > > > > [1] https://issues.apache.org/jira/browse/FLINK-29932 > > [2] https://issues.apache.org/jira/browse/FLINK-21239 > > [3] https://issues.apache.org/jira/browse/FLINK-20873 > > > > > -- > > Best, > Benchao Li >
Re: [ANNOUNCE] New Apache Flink Committer - Sergey Nuyanzin
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: > 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 active and focused on adding > > and reviewing changes to the Flink SQL ecosystem. > > > > Currently, he is upgrading Flink's SQL engine to the latest Apache > > Calcite version [1][2][3] and helps in updating other project-wide > > dependencies as well. > > > > Please join me in congratulating Sergey Nuyanzin for becoming a Flink > > Committer! > > > > Best, > > Timo Walther (on behalf of the Flink PMC) > > > > [1] https://issues.apache.org/jira/browse/FLINK-29932 > > [2] https://issues.apache.org/jira/browse/FLINK-21239 > > [3] https://issues.apache.org/jira/browse/FLINK-20873 > > > > > -- > > Best, > Benchao Li >
Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements
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. > > > 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 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 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 collected so far, which are supported > on > > > other big data engines, such as spark, hive or presto. I wonder if we > can > > > support these abilities? > > > > > > In addition, the subject of this email is named 'Auxiliary Statements' > > > mainly because the alignment of these statements will not have much > > impact > > > on the core SQL runtime. > > > > > > Support or Not > > > > > > With Advanced Syntax Or Not (in/from or like) > > > > > > show create table > > > > > > Yes > > > > > > Yes > > > > > > show tables > > > > > > Yes > > > > > > Yes > > > > > > show columns > > > > > > Yes > > > > > > Yes > > > > > > show catalogs > > > > > > Yes > > > > > > without filter > > > > > > show databases > > > > > > Yes > > > > > > without filter > > > > > > show functions > > > > > > Yes > > > > > > without filter > > > > > > show views > > > > > > Yes > > > > > > without filter > > > > > > show modules > > > > > > Yes > > > > > > without filter > > > > > > show jars > > > > > > Yes > > > > > > without filter > > > > > > show jobs > > > > > > Yes > > > > > > without filter > > > > > > We can see current flink many sql statements only support showing with > > full > > > datas, without 'FROM/IN' or 'LIKE' filter clause. > > > > > > Support or Not > > > > > > describe database > > > > > > No > > > > > > describe table > > > > > > Yes > > > > > > describe function > > > > > > No > > > > > > describe query > > > > > > No > > > > > > current flink only supports describing tables. > > > > > > Also, please let me know if there is a mistake. Looking forward to your > > > reply. > > > > > > > > > Best Regards, > > > Ran Tao > > > https://github.com/chucheng92 > > > > >
Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements
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 Tue, 21 Feb 2023 at 19:37, Ran Tao wrote: > > > 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 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 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 collected so far, which are > supported > > on > > > > other big data engines, such as spark, hive or presto. I wonder if we > > can > > > > support these abilities? > > > > > > > > In addition, the subject of this email is named 'Auxiliary > Statements' > > > > mainly because the alignment of these statements will not have much > > > impact > > > > on the core SQL runtime. > > > > > > > > Support or Not > > > > > > > > With Advanced Syntax Or Not (in/from or like) > > > > > > > > show create table > > > > > > > > Yes > > > > > > > > Yes > > > > > > > > show tables > > > > > > > > Yes > > > > > > > > Yes > > > > > > > > show columns > > > > > > > > Yes > > > > > > > > Yes > > > > > > > > show catalogs > > > > > > > > Yes > > > > > > > > without filter > > > > > > > > show databases > > > > > > > > Yes > > > > > > > > without filter > > > > > > > > show functions > > > > > > > > Yes > > > > > > > > without filter > > > > > > > > show views > > > > > > > > Yes > > > > > > > > without filter > > > > > > > > show modules > > > > > > > > Yes > > > > > > > > without filter > > > > > > > > show jars > > > > > > > > Yes > > > > > > > > without filter > > > > > > > > show jobs > > > > > > > > Yes > > > > > > > > without filter > > > > > > > > We can see current flink many sql statements only support showing > with > > > full > > > > datas, without 'FROM/IN' or 'LIKE' filter clause. > > > > > > > > Support or Not > > > > > > > > describe database > > > > > > > > No > > > > > > > > describe table > > > > > > > > Yes > > > > > > > > describe function > > > > > > > > No > > > > > > > > describe query > > > > > > > > No > > > > > > > > current flink only supports describing tables. > > > > > > > > Also, please let me know if there is a mistake. Looking forward to > your > > > > reply. > > > > > > > > > > > > Best Regards, > > > > Ran Tao > > > > https://github.com/chucheng92 > > > > > > > > >
Re: [ANNOUNCE] New Apache Flink Committer - Sergey Nuyanzin
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 Committer - Sergey Nuyanzin > > 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 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 ecosystem. > > > > > > Currently, he is upgrading Flink's SQL engine to the latest Apache > > > Calcite version [1][2][3] and helps in updating other project-wide > > > dependencies as well. > > > > > > Please join me in congratulating Sergey Nuyanzin for becoming a Flink > > > Committer! > > > > > > Best, > > > Timo Walther (on behalf of the Flink PMC) > > > > > > [1] https://issues.apache.org/jira/browse/FLINK-29932 > > > [2] https://issues.apache.org/jira/browse/FLINK-21239 > > > [3] https://issues.apache.org/jira/browse/FLINK-20873 > > > > > > > > > -- > > > > Best, > > Benchao Li > > >
Connecting two jobs with socket over AWS EMR - How to define the ip? - cont'
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. The source generates records and succeeds to write records. The
destination doesn't read any records.
The socket try to connect to the private dns name ip-10-0-102-186.ec2.internal
or to 10.0.102.186
The reader IPs enumeration are:
2023-02-21 10:17:53,170 INFO org.example.WindowWordCount
[] - Address 2 172.18.0.1
2023-02-21 10:17:53,170 INFO org.example.WindowWordCount
[] - Address 2 172.17.0.1
2023-02-21 10:17:53,170 INFO org.example.WindowWordCount
[] - Address 2 fe80:0:0:0:c1c:daff:fe82:c3df%eth0
2023-02-21 10:17:53,170 INFO org.example.WindowWordCount
[] - Address 2 10.0.102.186
2023-02-21 10:17:53,170 INFO org.example.WindowWordCount
[] - Address 2 0:0:0:0:0:0:0:1%lo
2023-02-21 10:17:53,170 INFO org.example.WindowWordCount
[] - Address 2 127.0.0.1
The writer IPs enumeration are:
2023-02-21 10:17:58,809 INFO org.example.Main
[] - Address 2 172.18.0.1
2023-02-21 10:17:58,809 INFO org.example.Main
[] - Address 2 172.17.0.1
2023-02-21 10:17:58,809 INFO org.example.Main
[] - Address 2 fe80:0:0:0:c1c:daff:fe82:c3df%eth0
2023-02-21 10:17:58,809 INFO org.example.Main
[] - Address 2 10.0.102.186
2023-02-21 10:17:58,809 INFO org.example.Main
[] - Address 2 0:0:0:0:0:0:0:1%lo
2023-02-21 10:17:58,809 INFO org.example.Main
[] - Address 2 127.0.0.1
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 getting some
exception, can you add error logs. 3. Have you verified if your source is
generating new records when you are trying to view records in socket. Bests,
Samrat
Hi, I build a streaming pipeline and there are two jobs that I wish to connect
with socket(later we plan to have kafka instead). The jobs submitted in AWS EMR
cluster with this configuration { "Classification": "flink-conf", "Properties":
{ "JAVA_HOME": "/usr/lib/jvm/java-11-openjdk", "env.java.home":
"/usr/lib/jvm/java-11-openjdk", "high-availability": "zookeeper",
"high-availability.storageDir": "hdfs:///user/flink/recovery",
"high-availability.zookeeper.path.root": "/flink",
"high-availability.zookeeper.quorum": "%{hiera('hadoop::zk')}", "java.home":
"/usr/lib/jvm/java-11-openjdk", "taskmanager.data.port": "35001",
"taskmanager.numberOfTaskSlots": "2", "yarn.application-attempts": "10" } }, I
probably miss how to define the host when I use writeToSocket and
socketToStream from my jobs. Is it configuration or one of the primary/core
node ips. I have tried many options and non of the messages went through. Any
help would be appreciated.
Itay Sali
<>
<>
<>
<>
[jira] [Created] (FLINK-31168) JobManagerHAProcessFailureRecoveryITCase failed due to job not being found
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
Project: Flink
Issue Type: Bug
Components: Runtime / Coordination
Affects Versions: 1.15.3
Reporter: Matthias Pohl
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=46342&view=logs&j=b0a398c0-685b-599c-eb57-c8c2a771138e&t=747432ad-a576-5911-1e2a-68c6bedc248a&l=12706
We see this build failure because a job couldn't be found:
{code}
2023-02-21T02:55:31.2739440Z java.lang.RuntimeException:
java.util.concurrent.ExecutionException: java.lang.RuntimeException: Error
while waiting for job to be initialized
2023-02-21T02:55:31.2741768Zat
org.apache.flink.util.ExceptionUtils.rethrow(ExceptionUtils.java:319)
2023-02-21T02:55:31.2742818Zat
org.apache.flink.api.java.ExecutionEnvironment.executeAsync(ExecutionEnvironment.java:1061)
2023-02-21T02:55:31.2743733Zat
org.apache.flink.api.java.ExecutionEnvironment.execute(ExecutionEnvironment.java:958)
2023-02-21T02:55:31.2744521Zat
org.apache.flink.api.java.ExecutionEnvironment.execute(ExecutionEnvironment.java:942)
2023-02-21T02:55:31.2745563Zat
org.apache.flink.test.recovery.JobManagerHAProcessFailureRecoveryITCase.testJobManagerFailure(JobManagerHAProcessFailureRecoveryITCase.java:235)
2023-02-21T02:55:31.2751144Zat
org.apache.flink.test.recovery.JobManagerHAProcessFailureRecoveryITCase$4.run(JobManagerHAProcessFailureRecoveryITCase.java:336)
2023-02-21T02:55:31.2752388Z Caused by:
java.util.concurrent.ExecutionException: java.lang.RuntimeException: Error
while waiting for job to be initialized
2023-02-21T02:55:31.2753289Zat
java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
2023-02-21T02:55:31.2754081Zat
java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1999)
2023-02-21T02:55:31.2754759Zat
org.apache.flink.api.java.ExecutionEnvironment.executeAsync(ExecutionEnvironment.java:1056)
2023-02-21T02:55:31.2755241Z... 4 more
2023-02-21T02:55:31.2755787Z Caused by: java.lang.RuntimeException: Error while
waiting for job to be initialized
2023-02-21T02:55:31.2756673Zat
org.apache.flink.client.ClientUtils.waitUntilJobInitializationFinished(ClientUtils.java:160)
2023-02-21T02:55:31.2757958Zat
org.apache.flink.client.deployment.executors.AbstractSessionClusterExecutor.lambda$execute$2(AbstractSessionClusterExecutor.java:82)
2023-02-21T02:55:31.2758777Zat
org.apache.flink.util.function.FunctionUtils.lambda$uncheckedFunction$2(FunctionUtils.java:73)
2023-02-21T02:55:31.2759520Zat
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:642)
2023-02-21T02:55:31.2760203Zat
java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:479)
2023-02-21T02:55:31.2760844Zat
java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
2023-02-21T02:55:31.2761483Zat
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
2023-02-21T02:55:31.2762094Zat
java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
2023-02-21T02:55:31.2762687Zat
java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
2023-02-21T02:55:31.2763314Zat
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
2023-02-21T02:55:31.2764158Z Caused by:
java.util.concurrent.ExecutionException:
org.apache.flink.runtime.rest.util.RestClientException:
[org.apache.flink.runtime.rest.NotFoundException: Job
865dcd87f4828dbeb3d93eb52e2636b1 not found
2023-02-21T02:55:31.2765129Zat
org.apache.flink.runtime.rest.handler.job.AbstractExecutionGraphHandler.lambda$handleRequest$1(AbstractExecutionGraphHandler.java:99)
2023-02-21T02:55:31.2765993Zat
java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:986)
2023-02-21T02:55:31.2766699Zat
java.base/java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:970)
2023-02-21T02:55:31.2767578Zat
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
2023-02-21T02:55:31.2768398Zat
java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
2023-02-21T02:55:31.2769267Zat
org.apache.flink.runtime.rest.handler.legacy.DefaultExecutionGraphCache.lambda$getExecutionGraphInternal$0(DefaultExecutionGraphCache.java:109)
2023-02-21T02:55:31.2770090Zat
java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
2023-02-21T02:55:31.2770781Zat
java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(Comple
Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements
+ 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 to know the gap between Flink and other big data engines like Spark and what should be done. Best regards, Jing [1] https://spark.apache.org/docs/latest/sql-ref-syntax.html#auxiliary-statements On Tue, Feb 21, 2023 at 1:15 PM Ran Tao wrote: > 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 Tue, 21 Feb 2023 at 19:37, Ran Tao wrote: > > > > > 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 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 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 collected so far, which are > > supported > > > on > > > > > other big data engines, such as spark, hive or presto. I wonder if > we > > > can > > > > > support these abilities? > > > > > > > > > > In addition, the subject of this email is named 'Auxiliary > > Statements' > > > > > mainly because the alignment of these statements will not have much > > > > impact > > > > > on the core SQL runtime. > > > > > > > > > > Support or Not > > > > > > > > > > With Advanced Syntax Or Not (in/from or like) > > > > > > > > > > show create table > > > > > > > > > > Yes > > > > > > > > > > Yes > > > > > > > > > > show tables > > > > > > > > > > Yes > > > > > > > > > > Yes > > > > > > > > > > show columns > > > > > > > > > > Yes > > > > > > > > > > Yes > > > > > > > > > > show catalogs > > > > > > > > > > Yes > > > > > > > > > > without filter > > > > > > > > > > show databases > > > > > > > > > > Yes > > > > > > > > > > without filter > > > > > > > > > > show functions > > > > > > > > > > Yes > > > > > > > > > > without filter > > > > > > > > > > show views > > > > > > > > > > Yes > > > > > > > > > > without filter > > > > > > > > > > show modules > > > > > > > > > > Yes > > > > > > > > > > without filter > > > > > > > > > > show jars > > > > > > > > > > Yes > > > > > > > > > > without filter > > > > > > > > > > show jobs > > > > > > > > > > Yes > > > > > > > > > > without filter > > > > > > > > > > We can see current flink many sql statements only support showing > > with > > > > full > > > > > datas, without 'FROM/IN' or 'LIKE' filter clause. > > > > > > > > > > Support or Not > > > > > > > > > > describe database > > > > > > > > > > No > > > > > > > > > > describe table > > > > > > > > > > Yes > > > > > > > > > > describe function > > > > > > > > > > No > > > > > > > > > > describe query > > > > > > > > > > No > > > > > > > > > > current flink only supports describing tables. > > > > > > > > > > Also, please let me know if there is a mistake. Looking forward to > > your > > > > > reply. > > > > > > > > > > > > > > > Best Regards, > > > > > Ran Tao > > > > > https://github.com/chucheng92 > > > > > > > > > > > > > >
Re: [ANNOUNCE] New Apache Flink Committer - Sergey Nuyanzin
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" > > 收件人: "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: > > > > > 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 active and focused on > > adding > > > > and reviewing changes to the Flink SQL ecosystem. > > > > > > > > Currently, he is upgrading Flink's SQL engine to the latest Apache > > > > Calcite version [1][2][3] and helps in updating other project-wide > > > > dependencies as well. > > > > > > > > Please join me in congratulating Sergey Nuyanzin for becoming a Flink > > > > Committer! > > > > > > > > Best, > > > > Timo Walther (on behalf of the Flink PMC) > > > > > > > > [1] https://issues.apache.org/jira/browse/FLINK-29932 > > > > [2] https://issues.apache.org/jira/browse/FLINK-21239 > > > > [3] https://issues.apache.org/jira/browse/FLINK-20873 > > > > > > > > > > > > > -- > > > > > > Best, > > > Benchao Li > > > > > >
Re: [ANNOUNCE] New Apache Flink Committer - Sergey Nuyanzin
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: > > > > > 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: > > > > > > > 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 active and focused on > > > adding > > > > > and reviewing changes to the Flink SQL ecosystem. > > > > > > > > > > Currently, he is upgrading Flink's SQL engine to the latest Apache > > > > > Calcite version [1][2][3] and helps in updating other project-wide > > > > > dependencies as well. > > > > > > > > > > Please join me in congratulating Sergey Nuyanzin for becoming a > Flink > > > > > Committer! > > > > > > > > > > Best, > > > > > Timo Walther (on behalf of the Flink PMC) > > > > > > > > > > [1] https://issues.apache.org/jira/browse/FLINK-29932 > > > > > [2] https://issues.apache.org/jira/browse/FLINK-21239 > > > > > [3] https://issues.apache.org/jira/browse/FLINK-20873 > > > > > > > > > > > > > > > > > -- > > > > > > > > Best, > > > > Benchao Li > > > > > > > > > >
Re: [ANNOUNCE] New Apache Flink Committer - Sergey Nuyanzin
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 & 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 Committer - Sergey Nuyanzin > > > > > > > > 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 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 ecosystem. > > > > > > > > > > > > Currently, he is upgrading Flink's SQL engine to the latest > Apache > > > > > > Calcite version [1][2][3] and helps in updating other > project-wide > > > > > > dependencies as well. > > > > > > > > > > > > Please join me in congratulating Sergey Nuyanzin for becoming a > > Flink > > > > > > Committer! > > > > > > > > > > > > Best, > > > > > > Timo Walther (on behalf of the Flink PMC) > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/FLINK-29932 > > > > > > [2] https://issues.apache.org/jira/browse/FLINK-21239 > > > > > > [3] https://issues.apache.org/jira/browse/FLINK-20873 > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > Best, > > > > > Benchao Li > > > > > > > > > > > > > > >
[jira] [Created] (FLINK-31169) KubernetesResourceManagerDriverTest fails fatally due to 239 exit code
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: Flink
Issue Type: Bug
Components: Runtime / Coordination
Affects Versions: 1.17.0
Reporter: Matthias Pohl
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=46341&view=logs&j=5cae8624-c7eb-5c51-92d3-4d2dacedd221&t=5acec1b4-945b-59ca-34f8-168928ce5199&l=27329
{code}
[...]
Feb 21 04:44:11 [ERROR] Process Exit Code: 239
Feb 21 04:44:11 [ERROR] Crashed tests:
Feb 21 04:44:11 [ERROR]
org.apache.flink.kubernetes.KubernetesResourceManagerDriverTest
Feb 21 04:44:11 [ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:748)
[...]
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [ANNOUNCE] New Apache Flink Committer - Sergey Nuyanzin
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! > > > > > > 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" > > > > > 收件人: "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: > > > > > > > > > > > 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 active and focused > on > > > > > adding > > > > > > > and reviewing changes to the Flink SQL ecosystem. > > > > > > > > > > > > > > Currently, he is upgrading Flink's SQL engine to the latest > > Apache > > > > > > > Calcite version [1][2][3] and helps in updating other > > project-wide > > > > > > > dependencies as well. > > > > > > > > > > > > > > Please join me in congratulating Sergey Nuyanzin for becoming a > > > Flink > > > > > > > Committer! > > > > > > > > > > > > > > Best, > > > > > > > Timo Walther (on behalf of the Flink PMC) > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/FLINK-29932 > > > > > > > [2] https://issues.apache.org/jira/browse/FLINK-21239 > > > > > > > [3] https://issues.apache.org/jira/browse/FLINK-20873 > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > Best, > > > > > > Benchao Li > > > > > > > > > > > > > > > > > > > > >
Re: [VOTE] Apache Flink Kubernetes Operator Release 1.4.0, release candidate #1
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 + docker image from source successfully Best, Marton On Mon, Feb 20, 2023 at 2:58 PM Gyula Fóra wrote: > +1 (binding) > > - Downloaded archives, validated binary content, checksum signatures, > NOTICE files > - Installed to local k8s cluster from Helm repo, verified docker image, > logs > - Ran some basic examples, ran autoscaler example > > Cheers > Gyula > > On Sun, Feb 19, 2023 at 5:09 AM Peter Huang > wrote: > > > Thanks for preparing the release! > > > > +1 (non-binding) > > > > 1. Downloaded the archives, checksums, and signatures > > 2. Extract and inspect the source code for binaries > > 3. Compiled and tested the source code via mvn verify > > 4. Deployed helm chart from flink-kubernetes-operator-1.4.0-helm.tgz to > > local minikube cluster > > 5. Ran example jobs with V1_14, V1_15, V1_16, and verified operator logs > > 6. Built the docker container locally and verified it through repeatting > > step 5 > > > > Best Regards > > Peter Huang > > > > On Fri, Feb 17, 2023 at 8:53 PM Jim Busche wrote: > > > > > Thanks Gyula for the release. > > > > > > +1 (non-binding) > > > > > > > > > I tested the following: > > > > > > * Helm repo install from flink-kubernetes-operator-1.4.0-helm.tgz > > > * Podman Dockerfile build from source, looked good. > > > * Twistlock security scans of proposed image looks good. No > > currently > > > known vulnerabilities with the built image or > > > ghcr.io/apache/flink-kubernetes-operator:7fc23a1 > > > * UI, basic sample, basic session jobs look good. Logs look as > > > expected. > > > * Checksums looked good > > > * Tested OLM build/install on OpenShift 4.12 > > > * Verified that sessionjob correctly can write in the operator’s > > > /opt/flink/artifacts filesystem on OpenShift even in a non-default > > > namespace. > > > > > > > > > > > > Thanks, Jim > > > > > >
Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements
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 https://github.com/chucheng92 Jing Ge 于2023年2月21日周二 20:50写道： > + 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 to know the gap between Flink and > other big data engines like Spark and what should be done. > > Best regards, > Jing > > [1] > > https://spark.apache.org/docs/latest/sql-ref-syntax.html#auxiliary-statements > > On Tue, Feb 21, 2023 at 1:15 PM Ran Tao wrote: > > > 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 Tue, 21 Feb 2023 at 19:37, Ran Tao wrote: > > > > > > > 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 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 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 collected so far, which are > > > supported > > > > on > > > > > > other big data engines, such as spark, hive or presto. I wonder > if > > we > > > > can > > > > > > support these abilities? > > > > > > > > > > > > In addition, the subject of this email is named 'Auxiliary > > > Statements' > > > > > > mainly because the alignment of these statements will not have > much > > > > > impact > > > > > > on the core SQL runtime. > > > > > > > > > > > > Support or Not > > > > > > > > > > > > With Advanced Syntax Or Not (in/from or like) > > > > > > > > > > > > show create table > > > > > > > > > > > > Yes > > > > > > > > > > > > Yes > > > > > > > > > > > > show tables > > > > > > > > > > > > Yes > > > > > > > > > > > > Yes > > > > > > > > > > > > show columns > > > > > > > > > > > > Yes > > > > > > > > > > > > Yes > > > > > > > > > > > > show catalogs > > > > > > > > > > > > Yes > > > > > > > > > > > > without filter > > > > > > > > > > > > show databases > > > > > > > > > > > > Yes > > > > > > > > > > > > without filter > > > > > > > > > > > > show functions > > > > > > > > > > > > Yes > > > > > > > > > > > > without filter > > > > > > > > > > > > show views > > > > > > > > > > > > Yes > > > > > > > > > > > > without filter > > > > > > > > > > > > show modules > > > > > > > > > > > > Yes > > > > > > > > > > > > without filter > > > > > > > > > > > > show jars > > > > > > > > > > > > Yes > > > > > > > > > > > > without filter > > > > > > > > > > > > show jobs > > > > > > > > > > > > Yes > > > > > > > > > > > > without filter > > > > > > > > > > > > We can see current flink many sql statements only support showing > > > with > > > > > full > > > > > > datas, without 'FROM/IN' or 'LIKE' filter clause. > > > > > > > > > > > > Support or Not > > > > > > > > > > > > describe database > > > > > > > > > > > > No > > > > > > > > > > > > describe table > > > > > > > > > > > > Yes > > > > > > > > > > > > describe function > > > > > > > > > > > > No > > > > > > > > > > > > describe query > > > > > > > > > > > > No > > > > > > > > > > > > current flink only supports describing tables. > > > > > > > > > > > > Also, please let me know if there is a mistake. Looking forward > to > > > your > > > > > > reply. > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > Ran Tao > > > > > > https://github.com/chucheng92 > > > > > > > > > > > > > > > > > > > >
Re: [ANNOUNCE] New Apache Flink Committer - Anton Kalashnikov
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: > > > > > 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, Anton! > > > > > > > > > > Best, > > > > > Shammon > > > > > > > > > > On Tue, Feb 21, 2023 at 1:41 PM Sergey Nuyanzin < > snuyan...@gmail.com > > > > > > > > wrote: > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > On Tue, Feb 21, 2023 at 4:53 AM Weihua Hu < > huweihua@gmail.com> > > > > > wrote: > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > Best, > > > > > > > Weihua > > > > > > > > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 11:22 AM weijie guo < > > > > guoweijieres...@gmail.com > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > Weijie > > > > > > > > > > > > > > > > > > > > > > > > Leonard Xu 于2023年2月21日周二 11:02写道： > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > Leonard > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Feb 21, 2023, at 10:02 AM, Rui Fan > > > > > wrote: > > > > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > > Rui Fan > > > > > > > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 9:23 AM yuxia < > > > > > luoyu...@alumni.sjtu.edu.cn > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > >> Congrats Anton! > > > > > > > > > >> > > > > > > > > > >> Best regards, > > > > > > > > > >> Yuxia > > > > > > > > > >> > > > > > > > > > >> - 原始邮件 - > > > > > > > > > >> 发件人: "Matthias Pohl" > > > > > > > > > >> 收件人: "dev" > > > > > > > > > >> 发送时间: 星期二, 2023年 2 月 21日 上午 12:52:40 > > > > > > > > > >> 主题: Re: [ANNOUNCE] New Apache Flink Committer - Anton > > > > > Kalashnikov > > > > > > > > > >> > > > > > > > > > >> Congratulations, Anton! :-) > > > > > > > > > >> > > > > > > > > > >> On Mon, Feb 20, 2023 at 5:09 PM Jing Ge > > > > > > > > > > > > > > > > > > > > > > >> wrote: > > > > > > > > > >> > > > > > > > > > >>> Congrats Anton! > > > > > > > > > >>> > > > > > > > > > >>> On Mon, Feb 20, 2023 at 5:02 PM Samrat Deb < > > > > > > decordea...@gmail.com> > > > > > > > > > >> wrote: > > > > > > > > > >>> > > > > > > > > > congratulations Anton! > > > > > > > > > > > > > > > > > > Bests, > > > > > > > > > Samrat > > > > > > > > > > > > > > > > > > On Mon, 20 Feb 2023 at 9:29 PM, John Roesler < > > > > > > vvcep...@apache.org > > > > > > > > > > > > > > > > > >>> wrote: > > > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > -John > > > > > > > > > > > > > > > > > > > > On Mon, Feb 20, 2023, at 08:18, Piotr Nowojski wrote: > > > > > > > > > >> Hi, everyone > > > > > > > > > >> > > > > > > > > > >> On behalf of the PMC, I'm very happy to announce > Anton > > > > > > > Kalashnikov > > > > > > > > > >>> as a > > > > > > > > > > new > > > > > > > > > >> Flink Committer. > > > > > > > > > >> > > > > > > > > > >> Anton has been very active for almost two years > > already, > > > > > > > authored > > > > > > > > > >> and > > > > > > > > > >> reviewed many PRs over this time. He is active in > the > > > > > Flink's > > > > > > > > > >>> runtime, > > > > > > > > > >> being the main author of improvements like Buffer > > > > Debloating > > > > > > > > > >>> (FLIP-183) > > > > > > > > > >> [1], solved many bugs and fixed many test > > instabilities, > > > > > > > generally > > > > > > > > > > speaking > > > > > > > > > >> helping with the maintenance of runtime components. > > > > > > > > > >> > > > > > > > > > >> Please join me in congratulating Anton Kalashnikov > for > > > > > > becoming > > > > > > > a > > > > > > > > > >>> Flink > > > > > > > > > >> Committer! > > > > > > > > > >> > > > > > > > > > >> Best, > > > > > > > > > >> Piotr Nowojski (on behalf of the Flink PMC) > > > > > > > > > >> > > > > > > > > > >> [1] > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >>> > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-183%3A+Dynamic+buffer+size+adjustment > > > > > > > > > > > > > > > > > > > > > > > > > > > > >>> > > > > > > > > > >> > > > > >
[jira] [Created] (FLINK-31170) The spelling error of the document word causes sql to fail to execute
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 Issue Type: Improvement Components: Table SQL / API Affects Versions: 1.14.0 Reporter: BoYi Zhang Fix For: 1.14.7 Attachments: image-2023-02-21-21-14-18-486.png The spelling error of the document word causes sql to fail to execute !image-2023-02-21-21-14-18-486.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] Apache Flink Kubernetes Operator Release 1.4.0, release candidate #1
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 https://dist.apache.org/repos/dist/dev/flink/flink-kubernetes-operator-1.4.0-rc1/ 5. Ran example jobs with V1_16, and verified operator logs -- Best, Matt Wang Replied Message | From | Márton Balassi | | Date | 02/21/2023 21:07 | | To | | | Subject | Re: [VOTE] Apache Flink Kubernetes Operator Release 1.4.0, release candidate #1 | 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 + docker image from source successfully Best, Marton On Mon, Feb 20, 2023 at 2:58 PM Gyula Fóra wrote: +1 (binding) - Downloaded archives, validated binary content, checksum signatures, NOTICE files - Installed to local k8s cluster from Helm repo, verified docker image, logs - Ran some basic examples, ran autoscaler example Cheers Gyula On Sun, Feb 19, 2023 at 5:09 AM Peter Huang wrote: Thanks for preparing the release! +1 (non-binding) 1. Downloaded the archives, checksums, and signatures 2. Extract and inspect the source code for binaries 3. Compiled and tested the source code via mvn verify 4. Deployed helm chart from flink-kubernetes-operator-1.4.0-helm.tgz to local minikube cluster 5. Ran example jobs with V1_14, V1_15, V1_16, and verified operator logs 6. Built the docker container locally and verified it through repeatting step 5 Best Regards Peter Huang On Fri, Feb 17, 2023 at 8:53 PM Jim Busche wrote: Thanks Gyula for the release. +1 (non-binding) I tested the following: * Helm repo install from flink-kubernetes-operator-1.4.0-helm.tgz * Podman Dockerfile build from source, looked good. * Twistlock security scans of proposed image looks good. No currently known vulnerabilities with the built image or ghcr.io/apache/flink-kubernetes-operator:7fc23a1 * UI, basic sample, basic session jobs look good. Logs look as expected. * Checksums looked good * Tested OLM build/install on OpenShift 4.12 * Verified that sessionjob correctly can write in the operator’s /opt/flink/artifacts filesystem on OpenShift even in a non-default namespace. Thanks, Jim
Re: Proposal to improve the Apache Flink website
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 coupled to the design of the page or vice-versa. Please don't approach this as a "grand redesign" of the website where we'll just a flip a switch eventually to go from old to new. Rather, break down the "problems with the website" into separate issue that we can tackle one-by-one. Because of that I'd also be against creating a "committee" at this time, because that just makes it imo more likely that this will be handled as an all-or-nothing/waterfall kind of thing. On 21/02/2023 11:31, Maximilian Michels wrote: -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 amount of time to get it right. This can mean the project is unable to focus on the main target of delivering great software and documentation. Some concerns: 1. Content regressions (content not being displayed properly, content and graphics not fitting anymore, code formatting breaking) 2. Higher entry barrier for committing (tooling / formatting becomes complicated) 3. Lack of focus on the content which needs work too (e.g. outdated information, lack of documentation of features) That said, I would support a redesign if we prevent regressions and build on standard tooling and best practices. I'm just not convinced (yet) that the pros outweigh the cons. -Max On Tue, Feb 21, 2023 at 9:57 AM Danny Cranmer wrote: 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: 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 project. +1 looking forward to your proposal. Best regards, Jing [1] https://zeplin.io/ On Tue, Feb 21, 2023 at 8:59 AM Shuo Cheng wrote: Hey! +1 for the proposal, the first page of Flink is more like a tutorial document for developers compared to the other top apache projects. Looking forward to a more attractive Flink website. Best regards, Shuo On Tue, Feb 21, 2023 at 8:13 AM Mohan, Deepthi wrote: Hi, I am a product manager for Kinesis Data Analytics, AWS’s managed service for Apache Flink. I’m creating this thread to gauge community interest in redesigning the Flink website: https://flink.apache.org/. A few of our customers have provided feedback that the Apache Flink website looks dated. One customer claimed that the website looks “unwelcoming” and lacks useful graphics and colors. Another said it looks “like a wiki page thrown together by developers.” Customers also point out other related Apache project websites: https://spark.apache.org/ and https://kafka.apache.org/ as having “modern” user design. Many were surprised to hear that Flink has been a top-5 Apache project for several years now. As https://flink.apache.org/ is likely the first page someone new to Flink encounters, it will be helpful to modernize the look and feel of the website. Given the growing interest in Flink, we have an opportunity to make content and features visible and easily accessible to customers. I’d like to learn if this is an idea we should pursue. I can create a FLIP if there is interest. Thanks, Deepthi Mohan
Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements
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 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 > https://github.com/chucheng92 > > > Jing Ge 于2023年2月21日周二 20:50写道： > > > + 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 to know the gap between Flink and > > other big data engines like Spark and what should be done. > > > > Best regards, > > Jing > > > > [1] > > > > > https://spark.apache.org/docs/latest/sql-ref-syntax.html#auxiliary-statements > > > > On Tue, Feb 21, 2023 at 1:15 PM Ran Tao wrote: > > > > > 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 Tue, 21 Feb 2023 at 19:37, Ran Tao wrote: > > > > > > > > > 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 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 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 collected so far, which are > > > > supported > > > > > on > > > > > > > other big data engines, such as spark, hive or presto. I wonder > > if > > > we > > > > > can > > > > > > > support these abilities? > > > > > > > > > > > > > > In addition, the subject of this email is named 'Auxiliary > > > > Statements' > > > > > > > mainly because the alignment of these statements will not have > > much > > > > > > impact > > > > > > > on the core SQL runtime. > > > > > > > > > > > > > > Support or Not > > > > > > > > > > > > > > With Advanced Syntax Or Not (in/from or like) > > > > > > > > > > > > > > show create table > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > show tables > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > show columns > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > show catalogs > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > without filter > > > > > > > > > > > > > > show databases > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > without filter > > > > > > > > > > > > > > show functions > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > without filter > > > > > > > > > > > > > > show views > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > without filter > > > > > > > > > > > > > > show modules > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > without filter > > > > > > > > > > > > > > show jars > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > without filter > > > > > > > > > > > > > > show jobs > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > without filter > > > > > > > > > > > > > > We can see current flink many sql statements only support > showing > > > > with > > > > > > full > > > > > > > datas, without 'FROM/IN' or 'LIKE' filter clause. > > > > > > > > > > > > > > Support or Not > > > > > > > > > > > > > > describe database > > > > > > > > > > > > > > No > > > > > > > > > > > > > > describe table > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > describe function > > > > > > > > > > > > > > No > > > > > > > > > > > > > > describe query > > > > > > > > > > > > > >
Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements
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 INFORMATION_SCHEMA as the SQL standard defines it. Having a queryable table that contains metadata on which we can run arbitrary SQL logic not only filtering but aggregations like counting or projections. This would avoid touching the parser everytime and introduce more and more SQL keywords. What do you think? Regards, Timo On 21.02.23 14:32, Martijn Visser wrote: 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 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 https://github.com/chucheng92 Jing Ge 于2023年2月21日周二 20:50写道： + 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 to know the gap between Flink and other big data engines like Spark and what should be done. Best regards, Jing [1] https://spark.apache.org/docs/latest/sql-ref-syntax.html#auxiliary-statements On Tue, Feb 21, 2023 at 1:15 PM Ran Tao wrote: 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 Tue, 21 Feb 2023 at 19:37, Ran Tao wrote: 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 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 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 collected so far, which are supported on other big data engines, such as spark, hive or presto. I wonder if we can support these abilities? In addition, the subject of this email is named 'Auxiliary Statements' mainly because the alignment of these statements will not have much impact on the core SQL runtime. Support or Not With Advanced Syntax Or Not (in/from or like) show create table Yes Yes show tables Yes Yes show columns Yes Yes show catalogs Yes without filter show databases Yes without filter show functions Yes without filter show views Yes without filter show modules Yes without filter show jars Yes without filter show jobs Yes without filter We can see current flink many sql statements only support showing with full datas, without 'FROM/IN' or 'LIKE' filter clause. Support or Not describe database No describe table Yes describe function No describe query No current flink only supports describing tables. Also, please let me know if there is a mistake. Looking forward to your reply. Best Regards, Ran Tao https://github.com/chucheng92
Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements
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 way to solve this problem to avoid subsequent frequent changes to the parser module and keywords. Best Regards, Ran Tao https://github.com/chucheng92 Timo Walther 于2023年2月21日周二 22:58写道： > 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 > INFORMATION_SCHEMA as the SQL standard defines it. Having a queryable > table that contains metadata on which we can run arbitrary SQL logic not > only filtering but aggregations like counting or projections. > > This would avoid touching the parser everytime and introduce more and > more SQL keywords. > > What do you think? > > Regards, > Timo > > On 21.02.23 14:32, Martijn Visser wrote: > > 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 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 > >> https://github.com/chucheng92 > >> > >> > >> Jing Ge 于2023年2月21日周二 20:50写道： > >> > >>> + 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 to know the gap between Flink > and > >>> other big data engines like Spark and what should be done. > >>> > >>> Best regards, > >>> Jing > >>> > >>> [1] > >>> > >>> > >> > https://spark.apache.org/docs/latest/sql-ref-syntax.html#auxiliary-statements > >>> > >>> On Tue, Feb 21, 2023 at 1:15 PM Ran Tao wrote: > >>> > 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 Tue, 21 Feb 2023 at 19:37, Ran Tao wrote: > > > >> 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 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 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 collected so far, which are > > supported > >> on > other big data engines, such as spark, hive or presto. I wonder > >>> if > we > >> can > support these abilities? > > In addition, the subject of this email is named 'Auxiliary > > Statements' > mainly because the alignment of these statements will not have > >>> much > >>> impact > on the core SQL runtime. > > Support or Not > > With Advanced Syntax Or Not (in/from or like) > > show create table > > Yes > > Yes > > show tables > > Yes > > Yes > > show columns > > Yes > > Yes > > show catalogs > > Yes > > without filter > > show d
[jira] [Created] (FLINK-31171) Support iterate in Python DataStream API
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 Components: API / Python Reporter: Dian Fu The aim of this ticket is to support [iterate|https://nightlies.apache.org/flink/flink-docs-release-1.16/docs/dev/datastream/operators/overview/#iterate] in Python DataStream API. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-31172) Support coGroup in Python DataStream API
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 Components: API / Python Reporter: Dian Fu The aim of this ticket is support [coGroup|https://nightlies.apache.org/flink/flink-docs-release-1.16/docs/dev/datastream/operators/overview/#window-cogroup] in Python DataStream API. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [ANNOUNCE] New Apache Flink Committer - Sergey Nuyanzin
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 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: > > > > > > > > > > > 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 < > libenc...@apache.org> > > > > > 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 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 ecosystem. > > > > > > > > > > > > > > > > Currently, he is upgrading Flink's SQL engine to the latest > > > Apache > > > > > > > > Calcite version [1][2][3] and helps in updating other > > > project-wide > > > > > > > > dependencies as well. > > > > > > > > > > > > > > > > Please join me in congratulating Sergey Nuyanzin for > becoming a > > > > Flink > > > > > > > > Committer! > > > > > > > > > > > > > > > > Best, > > > > > > > > Timo Walther (on behalf of the Flink PMC) > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/FLINK-29932 > > > > > > > > [2] https://issues.apache.org/jira/browse/FLINK-21239 > > > > > > > > [3] https://issues.apache.org/jira/browse/FLINK-20873 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > Best, > > > > > > > Benchao Li > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [ANNOUNCE] New Apache Flink Committer - Anton Kalashnikov
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 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日周二 15:05写道： > > > > > > > > > Congratulations, Anton! > > > > > > > > > > Best, > > > > > Guowei > > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 1:52 PM Shammon FY > > wrote: > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > Best, > > > > > > Shammon > > > > > > > > > > > > On Tue, Feb 21, 2023 at 1:41 PM Sergey Nuyanzin < > > snuyan...@gmail.com > > > > > > > > > > wrote: > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 4:53 AM Weihua Hu < > > huweihua@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > Best, > > > > > > > > Weihua > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 11:22 AM weijie guo < > > > > > guoweijieres...@gmail.com > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > > > Weijie > > > > > > > > > > > > > > > > > > > > > > > > > > > Leonard Xu 于2023年2月21日周二 11:02写道： > > > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > > Leonard > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Feb 21, 2023, at 10:02 AM, Rui Fan < > fan...@apache.org > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > > > Rui Fan > > > > > > > > > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 9:23 AM yuxia < > > > > > > luoyu...@alumni.sjtu.edu.cn > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > >> Congrats Anton! > > > > > > > > > > >> > > > > > > > > > > >> Best regards, > > > > > > > > > > >> Yuxia > > > > > > > > > > >> > > > > > > > > > > >> - 原始邮件 - > > > > > > > > > > >> 发件人: "Matthias Pohl" > > > > > > > > > > >> 收件人: "dev" > > > > > > > > > > >> 发送时间: 星期二, 2023年 2 月 21日 上午 12:52:40 > > > > > > > > > > >> 主题: Re: [ANNOUNCE] New Apache Flink Committer - Anton > > > > > > Kalashnikov > > > > > > > > > > >> > > > > > > > > > > >> Congratulations, Anton! :-) > > > > > > > > > > >> > > > > > > > > > > >> On Mon, Feb 20, 2023 at 5:09 PM Jing Ge > > > > > > > > > > > > > > > > > > > > > > > > > >> wrote: > > > > > > > > > > >> > > > > > > > > > > >>> Congrats Anton! > > > > > > > > > > >>> > > > > > > > > > > >>> On Mon, Feb 20, 2023 at 5:02 PM Samrat Deb < > > > > > > > decordea...@gmail.com> > > > > > > > > > > >> wrote: > > > > > > > > > > >>> > > > > > > > > > > congratulations Anton! > > > > > > > > > > > > > > > > > > > > Bests, > > > > > > > > > > Samrat > > > > > > > > > > > > > > > > > > > > On Mon, 20 Feb 2023 at 9:29 PM, John Roesler < > > > > > > > vvcep...@apache.org > > > > > > > > > > > > > > > > > > > >>> wrote: > > > > > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > -John > > > > > > > > > > > > > > > > > > > > > > On Mon, Feb 20, 2023, at 08:18, Piotr Nowojski > wrote: > > > > > > > > > > >> Hi, everyone > > > > > > > > > > >> > > > > > > > > > > >> On behalf of the PMC, I'm very happy to announce > > Anton > > > > > > > > Kalashnikov > > > > > > > > > > >>> as a > > > > > > > > > > > new > > > > > > > > > > >> Flink Committer. > > > > > > > > > > >> > > > > > > > > > > >> Anton has been very active for almost two years > > > already, > > > > > > > > authored > > > > > > > > > > >> and > > > > > > > > > > >> reviewed many PRs over this time. He is active in > > the > > > > > > Flink's > > > > > > > > > > >>> runtime, > > > > > > > > > > >> being the main author of improvements like Buffer > > > > > Debloating > > > > > > > > > > >>> (FLIP-183) > > > > > > > > > > >> [1], solved many bugs and fixed many test > > > instabilities, > > > > > > > > generally > > > > > > > > > > > speaking > > > > > > > > > > >> helping with the maintenance of runtime > components. > > > > > > > > > > >> > > > > > > > > > > >> Please join me in congratulating Anton Kalashnikov > > for > > > > > > > becoming > > > > > > > > a > > > > > > > > > > >>> Flink > > > > > > > > > > >> Committer! > > > > > > > > > > >> > > > > > > > > > > >> Best, > > > > > > > > > > >> Piotr Nowojski (on behalf
Re: [ANNOUNCE] New Apache Flink Committer - Rui Fan
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 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: > > > > > > > >> Congrats Rui! > > > >> > > > >> On Mon, Feb 20, 2023 at 3:19 PM Piotr Nowojski < > pnowoj...@apache.org> > > > >> wrote: > > > >> > > > >>> Hi, everyone > > > >>> > > > >>> On behalf of the PMC, I'm very happy to announce Rui Fan as a new > Flink > > > >>> Committer. > > > >>> > > > >>> Rui Fan has been active on a small scale since August 2019, and > ramped > > > up > > > >>> his contributions in the 2nd half of 2021. He was mostly involved > in > > > >> quite > > > >>> demanding performance related work around the network stack and > > > >>> checkpointing, like re-using TCP connections [1], and many crucial > > > >>> improvements to the unaligned checkpoints. Among others: FLIP-227: > > > >> Support > > > >>> overdraft buffer [2], Merge small ChannelState file for Unaligned > > > >>> Checkpoint [3], Timeout aligned to unaligned checkpoint barrier in > the > > > >>> output buffers [4]. > > > >>> > > > >>> Please join me in congratulating Rui Fan for becoming a Flink > > > Committer! > > > >>> > > > >>> Best, > > > >>> Piotr Nowojski (on behalf of the Flink PMC) > > > >>> > > > >>> [1] https://issues.apache.org/jira/browse/FLINK-22643 > > > >>> [2] > > > >>> > > > >>> > > > >> > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-227%3A+Support+overdraft+buffer > > > >>> [3] https://issues.apache.org/jira/browse/FLINK-26803 > > > >>> [4] https://issues.apache.org/jira/browse/FLINK-27251 > > > >>> > > > >
Re: Proposal to improve the Apache Flink website
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 2/21/23, 5:31 AM, "Chesnay Schepler" wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. 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 coupled to the design of the page or vice-versa. Please don't approach this as a "grand redesign" of the website where we'll just a flip a switch eventually to go from old to new. Rather, break down the "problems with the website" into separate issue that we can tackle one-by-one. Because of that I'd also be against creating a "committee" at this time, because that just makes it imo more likely that this will be handled as an all-or-nothing/waterfall kind of thing. On 21/02/2023 11:31, Maximilian Michels wrote: > -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 amount of time to > get it right. This can mean the project is unable to focus on the main > target of delivering great software and documentation. > > Some concerns: > 1. Content regressions (content not being displayed properly, content > and graphics not fitting anymore, code formatting breaking) > 2. Higher entry barrier for committing (tooling / formatting becomes > complicated) > 3. Lack of focus on the content which needs work too (e.g. outdated > information, lack of documentation of features) > > That said, I would support a redesign if we prevent regressions and > build on standard tooling and best practices. I'm just not convinced > (yet) that the pros outweigh the cons. > > -Max > > On Tue, Feb 21, 2023 at 9:57 AM Danny Cranmer wrote: >> 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: >> >>> 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 project. >>> >>> +1 looking forward to your proposal. >>> >>> Best regards, >>> Jing >>> >>> [1] https://zeplin.io/ >>> >>> On Tue, Feb 21, 2023 at 8:59 AM Shuo Cheng wrote: >>> Hey! +1 for the proposal, the first page of Flink is more like a tutorial document for developers compared to the other top apache projects. >>> Looking forward to a more attractive Flink website. Best regards, Shuo On Tue, Feb 21, 2023 at 8:13 AM Mohan, Deepthi >>> >>> wrote: > Hi, > > I am a product manager for Kinesis Data Analytics, AWS’s managed >>> service > for Apache Flink. I’m creating this thread to gauge community interest >>> in > redesigning the Flink website: https://flink.apache.org/. > A few of our customers have provided feedback that the Apache Flink > website looks dated. One customer claimed that the website looks > “unwelcoming” and lacks useful graphics and colors. Another said it >>> looks > “like a wiki page thrown together by developers.” Customers also point out > other related Apache project websites: https://spark.apache.org/ and > https://kafka.apache.org/ as having “modern” user design. Many were > surprised to hear that Flink has been a top-5 Apache project for >>> several > years now. > As https://flink.apache.org/ is likely the first page someone new to > Flink encounters, it will be helpful to modernize the look and feel of the > website. Given the g
[DISCUSS] FLIP-296: Watermark options for table API & SQL
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 watermark options in table API & SQL via SQL hint named 'WATERMARK_PARAMS' to support features: 1、Configurable watermark emit strategy 2、Dealing with idle sources 3、Watermark alignment Last but not least, thanks to Qingsheng and Jing Zhang for the initial reviews. Looking forward to your thoughts and any feedback is appreciated! [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=240884405 Best Yuan Kui
[jira] [Created] (FLINK-31173) TailOperator should only have one input
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 Components: Library / Machine Learning Affects Versions: ml-2.1.0, ml-2.0.0, ml-2.2.0 Reporter: Zhipeng Zhang In flink-ml-iteration, we have added a Tail operator to increment the epoch watermark at each iteration. We have made an assumption that each Tail operator have only one input and did not align the epoch watermarks from different inputs. This assumption might not be true if the input is an `union`. I propose to add an explicit check to prevent from having multiple input for the TailOperator. If a the input does contain multiple inputs, then users can add a map operator after union. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [DISCUSS] FLIP-296: Watermark options for table API & SQL
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 Sent: Wednesday, February 22, 2023 10:22 To: dev@flink.apache.org Subject: [DISCUSS] FLIP-296: Watermark options for table API & SQL 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 watermark options in table API & SQL via SQL hint named 'WATERMARK_PARAMS' to support features: 1、Configurable watermark emit strategy 2、Dealing with idle sources 3、Watermark alignment Last but not least, thanks to Qingsheng and Jing Zhang for the initial reviews. Looking forward to your thoughts and any feedback is appreciated! [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=240884405 Best Yuan Kui
[jira] [Created] (FLINK-31174) [Doc] Inconsistent data format between flink-training-repo and learn-flink doc
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
Project: Flink
Issue Type: Improvement
Components: Documentation / Training
Affects Versions: 1.16.1
Reporter: CHEN Zhongpu
The data format specified in
[flink-training-repo|[https://github.com/apache/flink-training/tree/release-1.16]]
shows that a TaixRide is either a start or an end one with the eventTime.
However, the Java code in [Data Pipelines &
ETL|[https://nightlies.apache.org/flink/flink-docs-release-1.16/docs/learn-flink/etl/]]
tried to get both "startTime" and "endTime". But in fact, those are not
defined in flink-training-repo.
{code:java}
Interval rideInterval = new Interval(ride.startTime, ride.endTime); {code}
I think such inconsistency would puzzle new comers of Flink.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [ANNOUNCE] New Apache Flink Committer - Rui Fan
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 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 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: > > > > > > > >> Congrats Rui! > > > >> > > > >> On Mon, Feb 20, 2023 at 3:19 PM Piotr Nowojski < > pnowoj...@apache.org> > > > >> wrote: > > > >> > > > >>> Hi, everyone > > > >>> > > > >>> On behalf of the PMC, I'm very happy to announce Rui Fan as a new > Flink > > > >>> Committer. > > > >>> > > > >>> Rui Fan has been active on a small scale since August 2019, and > ramped > > > up > > > >>> his contributions in the 2nd half of 2021. He was mostly involved > in > > > >> quite > > > >>> demanding performance related work around the network stack and > > > >>> checkpointing, like re-using TCP connections [1], and many crucial > > > >>> improvements to the unaligned checkpoints. Among others: FLIP-227: > > > >> Support > > > >>> overdraft buffer [2], Merge small ChannelState file for Unaligned > > > >>> Checkpoint [3], Timeout aligned to unaligned checkpoint barrier in > the > > > >>> output buffers [4]. > > > >>> > > > >>> Please join me in congratulating Rui Fan for becoming a Flink > > > Committer! > > > >>> > > > >>> Best, > > > >>> Piotr Nowojski (on behalf of the Flink PMC) > > > >>> > > > >>> [1] https://issues.apache.org/jira/browse/FLINK-22643 > > > >>> [2] > > > >>> > > > >>> > > > >> > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-227%3A+Support+overdraft+buffer > > > >>> [3] https://issues.apache.org/jira/browse/FLINK-26803 > > > >>> [4] https://issues.apache.org/jira/browse/FLINK-27251 > > > >>> > > > >
[jira] [Created] (FLINK-31175) Fix link doesn't work in hive_reaad_write doc
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: Improvement Components: Documentation Affects Versions: 1.17.0 Reporter: Shengkai Fang Fix For: 1.17.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [ANNOUNCE] New Apache Flink Committer - Anton Kalashnikov
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 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 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日周二 15:05写道： > > > > > > > > > Congratulations, Anton! > > > > > > > > > > Best, > > > > > Guowei > > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 1:52 PM Shammon FY > > wrote: > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > Best, > > > > > > Shammon > > > > > > > > > > > > On Tue, Feb 21, 2023 at 1:41 PM Sergey Nuyanzin < > > snuyan...@gmail.com > > > > > > > > > > wrote: > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 4:53 AM Weihua Hu < > > huweihua@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > Best, > > > > > > > > Weihua > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 11:22 AM weijie guo < > > > > > guoweijieres...@gmail.com > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > > > Weijie > > > > > > > > > > > > > > > > > > > > > > > > > > > Leonard Xu 于2023年2月21日周二 11:02写道： > > > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > > Leonard > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Feb 21, 2023, at 10:02 AM, Rui Fan < > fan...@apache.org > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > > > Rui Fan > > > > > > > > > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 9:23 AM yuxia < > > > > > > luoyu...@alumni.sjtu.edu.cn > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > >> Congrats Anton! > > > > > > > > > > >> > > > > > > > > > > >> Best regards, > > > > > > > > > > >> Yuxia > > > > > > > > > > >> > > > > > > > > > > >> - 原始邮件 - > > > > > > > > > > >> 发件人: "Matthias Pohl" > > > > > > > > > > >> 收件人: "dev" > > > > > > > > > > >> 发送时间: 星期二, 2023年 2 月 21日 上午 12:52:40 > > > > > > > > > > >> 主题: Re: [ANNOUNCE] New Apache Flink Committer - Anton > > > > > > Kalashnikov > > > > > > > > > > >> > > > > > > > > > > >> Congratulations, Anton! :-) > > > > > > > > > > >> > > > > > > > > > > >> On Mon, Feb 20, 2023 at 5:09 PM Jing Ge > > > > > > > > > > > > > > > > > > > > > > > > > >> wrote: > > > > > > > > > > >> > > > > > > > > > > >>> Congrats Anton! > > > > > > > > > > >>> > > > > > > > > > > >>> On Mon, Feb 20, 2023 at 5:02 PM Samrat Deb < > > > > > > > decordea...@gmail.com> > > > > > > > > > > >> wrote: > > > > > > > > > > >>> > > > > > > > > > > congratulations Anton! > > > > > > > > > > > > > > > > > > > > Bests, > > > > > > > > > > Samrat > > > > > > > > > > > > > > > > > > > > On Mon, 20 Feb 2023 at 9:29 PM, John Roesler < > > > > > > > vvcep...@apache.org > > > > > > > > > > > > > > > > > > > >>> wrote: > > > > > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > -John > > > > > > > > > > > > > > > > > > > > > > On Mon, Feb 20, 2023, at 08:18, Piotr Nowojski > wrote: > > > > > > > > > > >> Hi, everyone > > > > > > > > > > >> > > > > > > > > > > >> On behalf of the PMC, I'm very happy to announce > > Anton > > > > > > > > Kalashnikov > > > > > > > > > > >>> as a > > > > > > > > > > > new > > > > > > > > > > >> Flink Committer. > > > > > > > > > > >> > > > > > > > > > > >> Anton has been very active for almost two years > > > already, > > > > > > > > authored > > > > > > > > > > >> and > > > > > > > > > > >> reviewed many PRs over this time. He is active in > > the > > > > > > Flink's > > > > > > > > > > >>> runtime, > > > > > > > > > > >> being the main author of improvements like Buffer > > > > > Debloating > > > > > > > > > > >>> (FLIP-183) > > > > > > > > > > >> [1], solved many bugs and fixed many test > > > instabilities, > > > > > > > > generally > > > > > > > > > > > speaking > > > > > > > > > > >> helping with the maintenance of runtime > components. > > > > > > > > > > >> > > > > > > > > > > >> Please join me in congratulating Anton Kalashnikov > >
[jira] [Created] (FLINK-31176) correct the description of sql gateway configuration
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: Improvement Components: Documentation, Table SQL / Gateway Affects Versions: 1.16.0 Reporter: wangkang Attachments: image-2023-02-22-11-17-08-611.png correct the description of sql gateway configuration: 1.sql-gateway.session.idle-timeout 、sql-gateway.session.check-interval description in SqlGatewayServiceConfigOptions 2.GetSessionConfigHeaders and TriggerSessionHeartbeatHeaders class description !image-2023-02-22-11-17-08-611.png|width=1708,height=688! when setting sql-gateway.session.idle-timeout to negative value,SqlGateway will throw NumberFormatException,beacause the TimeUtils.pasDuration method doesn't support the ne negative value,so we should remove the 'or negative value' description -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [DISCUSS] FLIP-296: Watermark options for table API & SQL
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 t2 /*+ WATERMARK PARAMS(‘rowtime’ = ’time_column’, ‘rowtime_expression’ = ’time_column - INTERVAL 5 SECOND') */ > 2023年2月22日 10:22，kui yuan 写道： > > 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 watermark options in table API & SQL via > SQL hint named 'WATERMARK_PARAMS' to support features: > > 1、Configurable watermark emit strategy > > 2、Dealing with idle sources > > 3、Watermark alignment > > > Last but not least, thanks to Qingsheng and Jing Zhang for the initial > reviews. > > > Looking forward to your thoughts and any feedback is appreciated! > > > [1] > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=240884405 > > > Best > > Yuan Kui
Re: [ANNOUNCE] New Apache Flink Committer - Rui Fan
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> > Subject: Re: [ANNOUNCE] New Apache Flink Committer - Rui Fan > > 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 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: > > > > > > > > > >> Congrats Rui! > > > > >> > > > > >> On Mon, Feb 20, 2023 at 3:19 PM Piotr Nowojski < > > pnowoj...@apache.org> > > > > >> wrote: > > > > >> > > > > >>> Hi, everyone > > > > >>> > > > > >>> On behalf of the PMC, I'm very happy to announce Rui Fan as a new > > Flink > > > > >>> Committer. > > > > >>> > > > > >>> Rui Fan has been active on a small scale since August 2019, and > > ramped > > > > up > > > > >>> his contributions in the 2nd half of 2021. He was mostly involved > > in > > > > >> quite > > > > >>> demanding performance related work around the network stack and > > > > >>> checkpointing, like re-using TCP connections [1], and many > crucial > > > > >>> improvements to the unaligned checkpoints. Among others: > FLIP-227: > > > > >> Support > > > > >>> overdraft buffer [2], Merge small ChannelState file for Unaligned > > > > >>> Checkpoint [3], Timeout aligned to unaligned checkpoint barrier > in > > the > > > > >>> output buffers [4]. > > > > >>> > > > > >>> Please join me in congratulating Rui Fan for becoming a Flink > > > > Committer! > > > > >>> > > > > >>> Best, > > > > >>> Piotr Nowojski (on behalf of the Flink PMC) > > > > >>> > > > > >>> [1] https://issues.apache.org/jira/browse/FLINK-22643 > > > > >>> [2] > > > > >>> > > > > >>> > > > > >> > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-227%3A+Support+overdraft+buffer > > > > >>> [3] https://issues.apache.org/jira/browse/FLINK-26803 > > > > >>> [4] https://issues.apache.org/jira/browse/FLINK-27251 > > > > >>> > > > > > > >
Re: [ANNOUNCE] New Apache Flink Committer - Anton Kalashnikov
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 Apache Flink Committer - Anton Kalashnikov > > 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 9:34 AM Martijn Visser < > martijnvis...@apache.org > > > > > > 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日周二 15:05写道： > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > Best, > > > > > > Guowei > > > > > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 1:52 PM Shammon FY > > > wrote: > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > Best, > > > > > > > Shammon > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 1:41 PM Sergey Nuyanzin < > > > snuyan...@gmail.com > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 4:53 AM Weihua Hu < > > > huweihua@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > Weihua > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 11:22 AM weijie guo < > > > > > > guoweijieres...@gmail.com > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > > > > > Weijie > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Leonard Xu 于2023年2月21日周二 11:02写道： > > > > > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > > > Leonard > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Feb 21, 2023, at 10:02 AM, Rui Fan < > > fan...@apache.org > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > > > > Rui Fan > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Feb 21, 2023 at 9:23 AM yuxia < > > > > > > > luoyu...@alumni.sjtu.edu.cn > > > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > >> Congrats Anton! > > > > > > > > > > > >> > > > > > > > > > > > >> Best regards, > > > > > > > > > > > >> Yuxia > > > > > > > > > > > >> > > > > > > > > > > > >> - 原始邮件 - > > > > > > > > > > > >> 发件人: "Matthias Pohl" .INVALID> > > > > > > > > > > > >> 收件人: "dev" > > > > > > > > > > > >> 发送时间: 星期二, 2023年 2 月 21日 上午 12:52:40 > > > > > > > > > > > >> 主题: Re: [ANNOUNCE] New Apache Flink Committer - > Anton > > > > > > > Kalashnikov > > > > > > > > > > > >> > > > > > > > > > > > >> Congratulations, Anton! :-) > > > > > > > > > > > >> > > > > > > > > > > > >> On Mon, Feb 20, 2023 at 5:09 PM Jing Ge > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> wrote: > > > > > > > > > > > >> > > > > > > > > > > > >>> Congrats Anton! > > > > > > > > > > > >>> > > > > > > > > > > > >>> On Mon, Feb 20, 2023 at 5:02 PM Samrat Deb < > > > > > > > > decordea...@gmail.com> > > > > > > > > > > > >> wrote: > > > > > > > > > > > >>> > > > > > > > > > > > congratulations Anton! > > > > > > > > > > > > > > > > > > > > > > Bests, > > > > > > > > > > > Samrat > > > > > > > > > > > > > > > > > > > > > > On Mon, 20 Feb 2023 at 9:29 PM, John Roesler < > > > > > > > > vvcep...@apache.org > > > > > > > > > > > > > > > > > > > > > >>> wrote: > > > > > > > > > > > > > > > > > > > > > > > Congratulations, Anton! > > > > > > > > > > > > -John > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Feb 20, 2023, at 08:18, Piotr Nowojski > > wrote: > > > > > > > > > > > >> Hi, everyone > > > > > > > > > > > >> > > > > > > > > > > > >> On behalf of the PMC, I'm very happy to announce > > > Anton > > > > > > > > > Kalashnikov > > > > > > > > > > > >>> as a > > > > > > > > > > > > new > > > > > > > > > > > >> Flink Committer. > > > > > > > > > > > >> > > > > > > > > > > > >> Anton has been very active for almost two years > > > > already, > > > > > > > > > authored > > > > > > > > > > > >> and > > > > > > > > > > > >> reviewed many PRs over this time. He is active > in > > > the > > > > > > > Flink's > > > > > > > > > > > >>> runtime, > > >
[jira] [Created] (FLINK-31177) To introduce a formatter for Markdown files
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: Improvement Reporter: CHEN Zhongpu Currently, markdown files in *docs* are maintained and updated by many contributors, and different people have varying code style taste. By the way, as the syntax of markdown is not really strict, the styles can also inconsistent. To name a few, * Some prefer `*` to make a list item, while others may prefer `-`. * It is common to leave many unnecessary blank lines and spaces. * To make a divider, the number of `-` can be varying. To this end, I think it would be nicer to encourage or demand contributors to format their markdown files before making a pull request. Personally, I think Prettier ([https://prettier.io/)] is a good candidate. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [DISCUSS] FLIP-296: Watermark options for table API & SQL
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 different watermark params, what will happen? For example, there is a source table T and user submit the following job SELECT T1.id, T1.cnt_val, T2.sum_val FROM (SELECT id, count(val) as cnt_val FROM T /*+ WATERMARK PARAMS(‘rowtime’ = ’time_column’, ‘rowtime_expression’ = ’time_column - INTERVAL 5 SECOND') */ GROUP BY id) T1 JOIN (SELECT id, sum(val) as sum_val FROM T /*+ WATERMARK PARAMS(‘rowtime’ = ’time_column’, ‘rowtime_expression’ = ’time_column - INTERVAL 10 SECOND') */ GROUP BY id) T2 ON T1.id=T2.id Best, Shammon On Wed, Feb 22, 2023 at 11:28 AM 郑舒力 wrote: > 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 t2 /*+ WATERMARK PARAMS(‘rowtime’ = ’time_column’, > ‘rowtime_expression’ = ’time_column - INTERVAL 5 SECOND') */ > > > > > 2023年2月22日 10:22，kui yuan 写道： > > > > 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 watermark options in table API & SQL via > > SQL hint named 'WATERMARK_PARAMS' to support features: > > > > 1、Configurable watermark emit strategy > > > > 2、Dealing with idle sources > > > > 3、Watermark alignment > > > > > > Last but not least, thanks to Qingsheng and Jing Zhang for the initial > > reviews. > > > > > > Looking forward to your thoughts and any feedback is appreciated! > > > > > > [1] > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=240884405 > > > > > > Best > > > > Yuan Kui > >
[jira] [Created] (FLINK-31178) Public Writer API
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 Components: Table Store Reporter: Jingsong Lee Assignee: Jingsong Lee Fix For: table-store-0.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-31179) Make data structures serializable
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 Components: Table Store Reporter: Jingsong Lee Assignee: Jingsong Lee Fix For: table-store-0.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-31180) Fail early when installing minikube and check whether we can retry
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 Issue Type: Improvement Components: Test Infrastructure Affects Versions: 1.16.1, 1.15.3, 1.17.0 Reporter: Matthias Pohl https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=46367&view=logs&j=bea52777-eaf8-5663-8482-18fbc3630e81&t=b2642e3a-5b86-574d-4c8a-f7e2842bfb14&l=4726 We experienced a build failure where Minikube couldn't be installed due to some network issues. Two things which we could do here: * check whether we can add a retry loop (maybe also to other resource) * fail early if CI didn't manage to install the binaries -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [ANNOUNCE] New Apache Flink Committer - Sergey Nuyanzin
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: > > > > > 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 & well-deserved! :) > > > > > > > > > > > > On Tue, Feb 21, 2023 at 1:03 PM yuxia < > luoyu...@alumni.sjtu.edu.cn > > > > > > > > wrote: > > > > > > > > > > > > > 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 < > > libenc...@apache.org> > > > > > > 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 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 ecosystem. > > > > > > > > > > > > > > > > > > Currently, he is upgrading Flink's SQL engine to the latest > > > > Apache > > > > > > > > > Calcite version [1][2][3] and helps in updating other > > > > project-wide > > > > > > > > > dependencies as well. > > > > > > > > > > > > > > > > > > Please join me in congratulating Sergey Nuyanzin for > > becoming a > > > > > Flink > > > > > > > > > Committer! > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > Timo Walther (on behalf of the Flink PMC) > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/FLINK-29932 > > > > > > > > > [2] https://issues.apache.org/jira/browse/FLINK-21239 > > > > > > > > > [3] https://issues.apache.org/jira/browse/FLINK-20873 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > > Best, > > > > > > > > Benchao Li > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
