for further improvement.
Best regards,
Jing
On Mon, May 29, 2023 at 5:31 AM Feng Jin wrote:
> Hi all, I would like to update you on the latest progress of the FLIP.
>
>
> Last week, Leonard Xu, HangRuan, Jing Ge, Shammon FY, ShengKai Fang and I
> had an offline discussion regard
Thanks Qingsheng for taking care of this!
Best regards,
Jing
On Mon, May 29, 2023 at 4:24 AM Qingsheng Ren wrote:
> Hi Kurt,
>
> The permission has been granted. Feel free to reach out if you have any
> questions.
>
> Looking forward to your FLIP!
>
> Best,
> Qingsheng
>
> On Mon, May 29, 2023
est regards,
>
> Weijie
>
>
> [1]
> https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release
>
> [2] https://github.com/pypa/twine/issues/997
>
>
> Jing Ge 于2023年5月27日周六 00:15写道：
>
> > Hi Weijie,
> >
> > Thanks again for your effort. I w
Hi Qingsheng,
Could you grant Kurt rights for creating a new FLIP page? Thanks!
@Kurt
Thanks for reaching out. Please pay attention to the FLIP number you will
pick up and keep "Next FLIP number" on [1] up to date. Thanks!
Best regards,
Jing
[1]
+1 (non-binding)
- checked sign
- checked hash
- checked repos
- checked tag
- compiled from source
- check the web PR
Best regards,
Jing
On Sun, May 28, 2023 at 4:00 PM Benchao Li wrote:
> Thanks Martijn,
>
> - checked signature/checksum [OK]
> - downloaded src, compiled from source [OK]
>
> So, in conclusion, no new interface is introduced, but we extend the
> ability to support user-defined async table function.
>
> [1]:
>
> https://nightlies.apache.org/flink/flink-docs-release-1.17/docs/dev/table/functions/udfs/
> [2]: https://lists.apache.org/thread/qljwd40v5ntz6
Hi Aitozi,
Thanks for your proposal. I am not quite sure if I understood your thoughts
correctly. You described a special case implementation of the
AsyncTableFunction with on public API changes. Would you please elaborate
your purpose of writing a FLIP according to the FLIP documentation[1]?
Hi Hong,
Great question! Afaik, it depends on the implementation. Speaking of the
"loopback" event sending to the SplitEnumerator, I guess you meant here [1]
(It might be good, if you could point out the right position in the source
code to help us understand the question better:)), which will
Hi Weijie,
Thanks again for your effort. I was wondering if there were any obstacles
you had to overcome while releasing 1.16.2 and 1.17.1 that could lead us to
any improvement wrt the release process and management?
Best regards,
Jing
On Fri, May 26, 2023 at 4:41 PM Martijn Visser
wrote:
>
Hi Weijie,
That is earlier than I expected! Thank you so much for your effort!
Best regards,
Jing
On Fri, May 26, 2023 at 4:44 PM Martijn Visser
wrote:
> Same here as with Flink 1.16.2, thank you Weijie and those who helped with
> testing!
>
> On Fri, May 26, 2023 at 1:08 PM weijie guo
>
t; new image. I estimate that this may take 1-2 days and then I will
> officially announce the release of the new version immediately
>
> Best regards,
>
> Weijie
>
>
>
> Jing Ge 于2023年5月25日周四 19:42写道：
>
> > Hi Weijie,
> >
> > Thanks again for driving
gt; is
> > > running at the bounded stage, then Flink will use the "
> > > execution.checkpoint.interval.bounded" as the checkpointing interval.
> > >
> > > Here are the the concerns I have with this approach:
> > >
> > > - The exec
nce that we have unanimously approved this release.
>
>
>
> There are 7 approving votes, 3 of which are binding:
>
>
> * Xintong Song(binding)
>
> * Yuxin Tan
>
> * Xingbo Huang(binding)
>
> * Yun Tang
>
> * Jing Ge
>
> * Qingsheng Ren(binding)
Hi Kevin,
Thanks for reaching out. This question is not new and has been asked
many times previously. I have the same feeling as Gyula. There are ways to
provide zero downtime for Flink jobs, but commonly, I doubt if it is really
necessary.
If there might be some special use cases that really
Yuxin Tan
>
> * Yun Tang
>
> * Jing Ge
>
> * Xintong Song(binding)
>
> * Xingbo Huang(binding)
>
> * Qingsheng Ren(binding)
>
> * Samrat Deb
>
> * Hang Ruan
>
>
> There are no disapproving votes.
>
>
> I'll work on the steps to finalize t
Hi Yunfeng, Hi Dong
Thanks for the informative discussion! It is a rational requirement to set
different checkpoint intervals for different sources in a hybridSource. The
tiny downside of this proposal, at least for me, is that I have to
understand the upper-bound definition of the interval and
cc user ML to get more attention, since the plugin will be used by Flink
application developers.
Best regards,
Jing
On Mon, May 22, 2023 at 3:32 PM Jing Ge wrote:
> Hi Emre,
>
> Thanks for clarifying it. Afaiac, it is a quite interesting proposal,
> especially for Flink job de
ity acknowledgement/support for it. I believe working with
> the Flink community on this is key as we'd need their support/opinion to do
> this the right way and reach more Flink users.
>
> Thanks
> Emre
>
> On 21/05/2023, 16:48, "Jing Ge" j...@ververica.com.inva>LID>
+1(non-binding)
- Verified signatures
- Verified hashes
- Verified tag
- repos contain all necessary files
- built from source
- reviewed the PR
Best regards,
Jing
On Mon, May 22, 2023 at 1:32 PM Yun Tang wrote:
> +1 (non-binding)
>
>
> * Verified signatures.
> * Start a local
Hi Emre,
Thanks for your proposal. It looks very interesting! Please pay attention
that most connectors have been externalized. Will your proposed plug be
used for building Flink Connectors or Flink itself? Furthermore, it would
be great if you could elaborate features wrt best practices so that
+1(non-binding)
- reviewed Jira release notes
- built from source
- apache repos contain all necessary files
- verified signatures
- verified hashes
- verified tag
- reviewed PR
Best regards,
Jing
On Sat, May 20, 2023 at 11:51 AM Yun Tang wrote:
> +1 (non-binding)
>
>
> * Verified
y, while preparing the pull request for the blog post.
> The specific released time depends on the speed at which they are
> completed. VOTE thread will be launched no later than next Monday at the
> latest.
>
> Best regards,
>
> Weijie
>
>
> Jing Ge 于2023年5月19日周五 14:4
Hi David,
Thanks for driving this. I'd like to second Emre, especially the second
suggestion. In practice, the parallelism number could be big. Users will be
frustrated, if they have to click hundred or even more times in order to
reach the wished number. Anyone who will take over the design
6:10 AM Lijie Wang
> > wrote:
> >
> > > +1 for the release.
> > >
> > > Best,
> > > Lijie
> > >
> > > Jing Ge 于2023年5月15日周一 17:07写道：
> > >
> > > > +1 for releasing 1.17.1
> > > >
> > > &g
Hi Karthi,
Thanks for raising this proposal. It is a common use case to sink metric
"data" into downstream Prometheus. The description in the motivation
section is more or less misleading the discussion. I would suggest you
rephrase it, e.g. metrics (pre)processing via Flink is
The current
+1 for releasing 1.17.1
Best Regards,
Jing
On Thu, May 11, 2023 at 10:03 AM Martijn Visser
wrote:
> +1, thanks for volunteering!
>
> On Thu, May 11, 2023 at 9:23 AM Xintong Song
> wrote:
>
> > +1
> >
> > I'll help with the steps that require PMC privileges.
> >
> > Best,
> >
> > Xintong
> >
>
Great news! We can finally get rid of additional setup to use maven 3.8.
Thanks @Chesnay for your effort!
Best regards,
Jing
On Sat, May 13, 2023 at 5:12 AM David Anderson
wrote:
> Chesnay, thank you for all your hard work on this!
>
> David
>
> On Fri, May 12, 2023 at 4:03 PM Chesnay Schepler
Hi Zakelly,
I saw you sent at least 4 same emails for voting FLIP-306. I guess this one
should be the last one and the right one for us to vote right? BTW, based
on the sending time, 72 hours means to open the discussion until May 12th.
Best regards,
Jing
On Tue, May 9, 2023 at 8:24 PM Zakelly
Hi Tan,
Thanks for raising the suggestion. Proposals are always welcome. Flink is
very well documented which turns out the translation effort is big. Afaiu,
there are limited contributors in the community who could review content in
Korean. I am wondering how you will continuously move forward
+1
- built the source
- verified signature
- verified hash
- contains no compiled binaries
- checked tag
- web PR looks good
Best regards,
Jing
On Fri, May 5, 2023 at 9:14 AM Khanh Vu wrote:
> Sorry, the above report is supposed for flink-connector-gpc-pubsub-3.0.1
>
> -
>
rve as the default CatalogStore
> to save catalogs in memory and replace the functionality of
> Mapcatalogs.
> The previous plan that kept Mapcatalogs has been moved to
> Rejected Alternatives.
>
>
>
> Best,
> Feng
>
> On Sun, Apr 30, 2023 at 9:03 PM Jing Ge
Hi devs,
I'd like to share highlights synced on 05/02/2023
- Feature list: many features have been added to the list[1]. Double
checked new FLIPs that passed votes are already in the list.
- CI instabilities: First of all, there are currently 4 Blocker issues. 3
of them have already been
e
> could minimize the need for suppressions altogether.
>
> Cheers,
> Panagiotis
>
> On Sun, Apr 30, 2023 at 6:16 AM Jing Ge
> wrote:
>
> > Thanks @Panagiotis for the hint! Does it mean that those suppressions
> need
> > to be cleaned up continuously while we
been migrated to junit5.
Best regards,
Jing
On Wed, Apr 26, 2023 at 9:02 AM Panagiotis Garefalakis
wrote:
> Thanks for bringing this up! +1 for the proposal
>
> @Jing Ge -- we don't necessarily need to completely migrate to Junit5 (even
> though it would be ideal).
> We
hieve multi-instance
> non-conflicting scenarios. What do you think?
>
>
>
> Best,
> Feng
>
> On Thu, Apr 27, 2023 at 9:03 PM Jing Ge
> wrote:
>
> > Hi Feng,
> >
> > Thanks for working on the FLIP. There are still some NIT issues in the
> FLIP
> >
Hi Tanjialiang,
Like we discussed in another thread, please feel free to create a FLIP and
start further discussion. In case you need any access right to the wiki
page, please let me know, thanks.
Best regards,
Jing
On Sun, Apr 23, 2023 at 4:23 AM tanjialiang wrote:
> Hi, devs.
> Do anyone
tomatically renaming the table name for the user.
>
>
>
> --
>
> Best regards,
>
> Mang Zhang
>
>
>
> At 2023-04-24 15:41:31, "Jing Ge" wrote:
> >Hi Mang,
> >
> >
> >
> >Thanks for clarifying it. I am trying to understand your
Hi,
As far as I am concerned, it would be great to build two top level
categories for Flink 2.0 release.
1. Future - mainly new big features or architecture improvements to achieve
visions like streamhouse. This makes the 2.0 release be the 2.0 instead of
1.x release, i.e. the real intention of
?
Best regards,
Jing
On Thu, Apr 27, 2023 at 8:18 AM Tamir Sagi
wrote:
> More details about the JDK bug here
> https://bugs.openjdk.org/browse/JDK-8277529
>
> Related Jira ticket
> https://issues.apache.org/jira/browse/FLINK-24998
>
> ------
> *From:* J
Best
> Feng
>
>
>
> On Thu, Apr 13, 2023 at 8:52 AM Shammon FY wrote:
>
> > Hi Feng
> >
> > Thanks for your update.
> >
> > I found there are two options in `Proposed Changes`, can you put the
> > unselected option in `Rejected Alternati
This is a great idea, thanks for bringing this up. +1
Also +1 for Junit4. If I am not mistaken, it could only be done after the
Junit5 migration is done.
@Chesnay thanks for the hint. Do we have any doc about it? If not, it might
deserve one. WDYT?
Best regards,
Jing
On Wed, Apr 26, 2023 at
Thanks Xingtong and Jark for kicking off and driving the discussion! It is
really good to see we finally start talking about Flink 2.0. There are so
many great ideas that require breaking API changes and so many tech debts
need to be cleaned up. With the Flink 2.0 ahead, we will be more fast-paced
+1(binding)
Best regards,
Jing
On Tue, Apr 25, 2023 at 5:17 AM Rui Fan <1996fan...@gmail.com> wrote:
> +1 (binding)
>
> Best,
> Rui Fan
>
> On Tue, Apr 25, 2023 at 10:06 AM Biao Geng wrote:
>
> > +1 (non-binding)
> > Best,
> > Biao Geng
> >
> > Martijn Visser 于2023年4月24日周一 20:20写道：
> >
> > >
Hi Qingsheng,
Thanks for sharing the summary!
Best regards,
Jing
On Mon, Apr 24, 2023 at 1:50 PM Qingsheng Ren wrote:
> Hi devs,
>
> I'd like to share some highlights in the 1.18 release sync on 04/18/2023
> (Sorry for the late summary!):
>
> - Feature list: @contributors please add your
Thanks Chesnay for working on this. Would you like to share more info about
the JDK bug?
Best regards,
Jing
On Mon, Apr 24, 2023 at 11:39 AM Chesnay Schepler
wrote:
> As it turns out Kryo isn't a blocker; we ran into a JDK bug.
>
> On 31/03/2023 08:57, Chesnay Schepler wrote:
>
>
>
rameter, this
> provides different atomicity implementations in Batch and Stream modes.
> Not only to determine if atomicity is supported, but also to help select
> different TwoPhaseCatalogTable implementations to provide different levels
> of atomicity!
>
> Looking forward to
Hi Green,
Since FLIP-292 opened the door to do fine-grained tuning at operator level
for Flink SQL jobs, I would also suggest leveraging the compiled json to do
further config optimization like Yun Tang already mentioned. We should
consider making it(leveraging the compiled json plan) the stand
Congrats! Qingsheng!
Best regards,
Jing
On Mon, Apr 24, 2023 at 9:35 AM Zakelly Lan wrote:
> Congratulations, Qingsheng!
>
> Best regards,
> Zakelly
>
> On Mon, Apr 24, 2023 at 11:52 AM Matthias Pohl
> wrote:
> >
> > Congratulations, Qingsheng! :)
> >
> > On Mon, Apr 24, 2023, 05:17 Yangze
Congrats! Leonard!
Best regards,
Jing
On Mon, Apr 24, 2023 at 5:53 AM Matthias Pohl
wrote:
> Congrats, Leonard :)
>
> On Mon, Apr 24, 2023, 05:17 Yangze Guo wrote:
>
> > Congratulations, Leonard!
> >
> > Best,
> > Yangze Guo
> >
> > On Mon, Apr 24, 2023 at 10:05 AM Shuo Cheng wrote:
> > >
Hi Mang,
This is the FLIP I was looking forward to after FLIP-218. Thanks for
driving it. I have two questions and would like to know your thoughts,
thanks:
1. It looks like you found another way to design the atomic CTAS with new
serializable TwoPhaseCatalogTable instead of making Catalog
t to the FLIP.
>
>
> 3:
> Thanks for your input, I agree that we can dicuss it in a different FLIP.
>
>
>
> Best regards,
> Yuxia
>
> - 原始邮件 -
> 发件人: "Jing Ge"
> 收件人: "dev"
> 发送时间: 星期六, 2023年 4 月 08日 上午 3:05:11
> 主题:
Hi Feng,
Thanks for raising this FLIP. I am still confused after completely reading
the thread with following questions:
1. Naming confusion - registerCatalog() and addCatalog() have no big
difference based on their names. One of them is responsible for data
persistence. How about
+1 (binding)
Best Regards,
Jing
On Mon, Apr 10, 2023 at 12:27 PM Lincoln Lee wrote:
> +1 (binding)
>
> Best,
> Lincoln Lee
>
>
> Jane Chan 于2023年4月10日周一 18:06写道：
>
> > Hi developers,
> >
> > Thanks for all the feedback on FLIP-292: Enhance COMPILED PLAN to support
> > operator-level state TTL
Hi yuxia,
Thanks for raising this topic. It is indeed a useful feature. +1 for
having it in Flink. I have some small questions and it would be great if
related information could be described in the FLIP.
1. Speaking of data warehouse use cases, what is the benefit of using
TRUNCATE table
Hi,
Jingsong, Yanfei, please check, if you can view the doc. Thanks.
Best regards,
Jing
On Fri, Apr 7, 2023 at 2:19 PM Zakelly Lan wrote:
> Hi Yanfei,
>
> Thanks for your comments.
>
> > Does this result in a larger space amplification? Maybe a more
> suitable value can be determined through
on Google Drawings
> and it seems like it went private.
> Maybe you have the images in your browser cache if you can see them. I see
> that other FLIPs have their images uploaded to Confluence, I think that
> would be a better way to store them.
>
> Regards,
> Mate
>
> Jing
Hi David,
I just checked and both diagrams are still there. The last change of the
page was on Sep 18, 2022. Would you like to clean your cache or change to
another browser and try again?
Best regards,
Jing
On Tue, Apr 4, 2023 at 5:25 PM David Anderson wrote:
> Does anyone know what
Dear devs and users,
Today was the kickoff meeting for Flink 1.18 release cycle. I'd like to
share the info synced in the meeting.
Meeting schedule:
Zoom will be used with a 40 mins limit for each meeting. That should be
fine for now. We will check it again if we have an issue with the time
t;>> Hi everyone,
> >>>
> >>> I'd like to share some updates about release managers of Flink 1.18.
> >> Jing,
> >>> Konstantin, Sergey, Yun and I had a discussion offline and we reached a
> >>> consensus that having 5 release managers is a bit
Hi Jane,
Thanks for your clarification. +1 for using this feature for advanced use
cases.
Best regards,
Jing
On Mon, Apr 3, 2023 at 4:43 PM Jane Chan wrote:
> Hi Yisha,
>
> Thanks for your detailed explanation. Here are my thoughts.
>
> > I'm interested in how to design a graphical interface
syntax is not easy to extend
> especially for things beyond ANSI SQL standard. While for the 2nd option,
> in terms of practicality, given that JSON strings can be very long, I don't
> think it's as convenient as the EXECUTE PLAN
> '/foo/bar/compiled-plan.json' statement, which is already s
Wow, that is good news! Thanks Chesnay for your effort.
I'd like to ask the same question as what Matthias asked. Speaking of the
workflow, should we first push changes to the asf-staging branch and check
it at https://flink.staged.apache.org and then cp them to the asf-site?
Should there always
Congrats!
Best regards,
Jing
On Mon, Mar 27, 2023 at 2:32 PM Leonard Xu wrote:
> Congratulations!
>
>
> Best,
> Leonard
>
> On Mar 27, 2023, at 5:23 PM, Yu Li wrote:
>
> Dear Flinkers,
>
>
>
> As you may have noticed, we are pleased to announce that Flink Table Store
> has joined the Apache
Hi Konstantin,
Qingsheng and I would love to participate and join you as release managers
for 1.18.
Speaking of the timeline, since we will have a big feature release with
1.18, a feature freeze in the middle of July would be better. It is also
not far from your proposal.
Best regards,
Jing
Thanks Jane for driving this FLIP.
The FLIP is quite interesting. Since the execution plan has finer
granularity than the plain SQL script, Hints at SQL level might not be able
to touch specific operators, which turns out that the idea of leveraging
the compiled execution plan is brilliant.
Thanks Gordon for driving this! There is another PR related to Kafka
connector: https://github.com/apache/flink/pull/21965
Best regards,
Jing
On Fri, Mar 24, 2023 at 4:06 PM Tzu-Li (Gordon) Tai
wrote:
> Hi all,
>
> Now that Flink 1.17 has been released, and given that we've already synced
>
Thanks Qingsheng for driving this. +1 since there are no changes after
1.15.4
Best regards,
JIng
On Fri, Mar 24, 2023 at 10:34 AM Qingsheng Ren wrote:
> Hi devs,
>
> I'd like to start a discussion about marking Flink 1.15 as an end-of-life
> version, and take 1.15.4 directly as the final patch
Excellent work! Congratulations! Appreciate the hard work and contributions
of everyone in the Apache Flink community who helped make this release
possible. Looking forward to those new features. Cheers!
Best regards,
Jing
On Thu, Mar 23, 2023 at 10:24 AM Leonard Xu wrote:
> The Apache Flink
Hi,
Thanks Panagiotis for this FLIP and thanks for all valuable discussions.
I'd like to share my two cents:
- FailureListenerContext#addTag and FailureListenerContext#getTags. It
seems that we have to call getTags() and then do remove activities if we
want to delete any tags (according to the
+1 binding
Best regards,
Jing
On Mon, Mar 20, 2023 at 4:02 PM Jingsong Li wrote:
> +1 binding
>
> Jark Wu 于2023年3月20日 周一21:19写道：
>
> > +1 (binding)
> >
> > Best,
> > Jark
> >
> > > 2023年3月15日 17:42，Yun Tang 写道：
> > >
> > > +1 (binding)
> > >
> > > Thanks Kui for driving this work.
> > >
> > >
ure that it’s a minor doc issue and won’t block the release.
>
> Best,
> Leonard
>
> [1]https://issues.apache.org/jira/browse/FLINK-31519
>
> > On Mar 20, 2023, at 7:45 AM, Jing Ge wrote:
> >
> > Hi Qingsheng,
> >
> > While reviewing the a
,
Jing
[1] https://github.com/apache/flink-web/pull/618
[2]
https://github.com/apache/flink/blob/release-1.17/docs/content/docs/dev/datastream/event-time/generating_watermarks.md?plain=1#L308
On Sat, Mar 18, 2023 at 10:10 PM Jing Ge wrote:
> +1
>
> - Verified the signature
> - Ver
+1
- Verified the signature
- Verified hashes
- Verify that the source archives do not contain any binaries
- Built from the source code
- Verified web PR
- Checked jars in the staging repo
Best regards,
Jing
On Sat, Mar 18, 2023 at 9:11 AM Lijie Wang wrote:
> +1 (binding)
>
> - Built from
+1 (binding)
Best Regards,
Jing
On Mon, Mar 13, 2023 at 1:57 PM Hang Ruan wrote:
> +1 (non-binding)
>
> Best,
> Hang
>
> yuxia 于2023年3月13日周一 20:52写道：
>
> > +1 (binding)
> > Thanks Lincoln Lee for driving it.
> >
> > Best regards,
> > Yuxia
> >
> > - 原始邮件 -
> > 发件人: "Lincoln Lee"
> >
+1 (binding)
Best Regards,
JIng
On Mon, Mar 13, 2023 at 8:22 AM Jingsong Li wrote:
> +1 (binding)
>
> Not block voting.
> But comment about `Public Interface` in the FLIP: these classes may
> not be `Public interface`? I think they are just internal
> implementations.
>
> Best,
> Jingsong
>
>
Congrats, Yuxia!
Best regards,
Jing
On Mon, Mar 13, 2023 at 8:49 AM Martijn Visser
wrote:
> Congrats Yuxia, well deserved!
>
> On Mon, Mar 13, 2023 at 5:29 AM Jane Chan wrote:
>
> > Congratulations, Yuxia!
> >
> > Best,
> > Jane
> >
> > On Mon, Mar 13, 2023 at 12:26 PM Lincoln Lee
> > wrote:
sql
> > jobs. I think we will not use Flink-Jdbc-Driver in Flink-Jdbc-Connector
> to
> > read/write data in general. If users can read/write specific tables by
> > Flink-Jdbc-Driver, they can use these tables in their flink jobs
> directly.
> > Thanks
> >
> &
Hi, Shammon,
This FLIP is very interesting. Thanks for driving it! Just out of
curiosity, Could it be used in the Flink JDBC connector[1] after
doing the appropriate implementation there?
Best regards,
Jing
[1]
https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/table/jdbc/
On
Hi Lincoln,
sounds good to me. Thanks!
Best,
Jing
On Wed, Mar 8, 2023 at 2:01 PM Lincoln Lee wrote:
> Hi Jing,
> Agree with you that using formal terms can be easier to users, I've updated
> the FLIP[1], since this is only one of the application scenarios for
> partial insert, our java doc
Hi Lincoln,
This FLIP is already in a good shape. +1. Thanks for driving it. I just
have a very tiny comment, e.g. NIT. The "wide table" you mentioned in
the FLIP should be "denormalized table"[1] and fact tables in data
warehouse are commonly denormalized tables[2]. As far as I am concerned,
-alignment.allow- unaligned-source-splits`,
> but maybe these behaviors are not understood by everyone, I will add some
> tips about flip-217 in the flip to let users understand the behavior in the
> case of source splits.
>
>
> Best,
>
> Kui Yuan
>
> Jing Ge 于2023年
+1
Thanks!
Best regards,
Jing
On Tue, Mar 7, 2023 at 9:51 AM ConradJam wrote:
> +1 (non-binding).
>
> Hang Ruan 于2023年3月7日周二 16:14写道：
>
> > Thanks for Ran's work.
> > +1 (non-binding).
> >
> > Best,
> > Hang
> >
> > Ran Tao 于2023年3月7日周二 15:59写道：
> >
> > > thanks Lau.
> > >
> > > The vote
> this solution will support aligning splits/partitions/shards [1]. Did I
> > miss anything?
>
> Best
> Kui Yuan
>
> [1] the POC:
> https://github.com/yuchengxin/flink/tree/yuankui/watermark_params
> [2] FLIP-217:
>
> https://cwiki.apache.org/confluence/display/FLINK/F
Hi,
Thanks Kui for driving this Flip and thanks all for the informative
discussion.
@Timo
Your suggestion about the naming convention is excellent. Thanks! I was
wondering why you, exceptionally, suggested 'scan.idle-timeout' instead of
'scan.watermark.idle-timeout'. I must miss something here.
Thanks Danny,
+1 (non-binding)
- GPG signatures looks good
- checked dist and maven repo
- maven clean install from source
- checked version consistency in pom files
- went through the web release notes and found one task is still open:
FLINK-31133 [1]
- download artifacts
-
Hi,
I have to agree with what Huang and Jingsong said. We should think more
about it from the user's(developers who use the API) perspective. The first
method T deserialize(byte[]) is convenient for users to deserialize a
single event. Many formats are using it, i.e. Avro, csv, etc. There should
en current some existed show operations
> need to be addressed either.
> @about ShowOperation with like. it's a good idea. yes, two parameters for
> constructor can work. thanks for your advice.
>
>
> Best Regards,
> Ran Tao
>
>
> Jing Ge 于2023年2月27日周一 06:29写道：
>
> &g
+1 (non-binding)
BTW, should we follow the content style [1] to describe the new rule using
1.2.x, 1.1.y, 1.1.z?
[1] https://flink.apache.org/downloads/#update-policy-for-old-releases
Best regards,
Jing
On Mon, Feb 27, 2023 at 1:06 PM Matthias Pohl
wrote:
> Thanks, Danny. Sounds good to me.
ozi
> > > >> > > >
> > > >> > > >
> > > >> > > > Ran Tao 于2023年2月23日周四 23:44写道：
> > > >> > > >
> > > >> > > > > Hi, JingSong, Jing.
> > > >> > > > >
> >
. This kind of usage occurs frequently in flink.
Looking forward to your other considerations,
and also try to wait to see if there are other relevant API
designers
or
committers to provide comments.
Best Regards,
Ran Tao
Jing Ge 于2023年2月23日周四 18:58写道：
Hi Jingson,
Thanks for sharing your thou
Congrats Martijn! You have made great progress. Thanks for your effort!
Best regards,
Jing
On Thu, Feb 23, 2023 at 8:47 PM Konstantin Knauf wrote:
> Thanks, Martijn. That was a lot of work.
>
> Am Do., 23. Feb. 2023 um 16:33 Uhr schrieb Maximilian Michels <
> m...@apache.org>:
>
> > Congrats!
r.
>
> [1] https://github.com/DavidAnson/markdownlint
>
> [2] https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md
>
>
> On 2023/02/22 21:22:02 Jing Ge wrote:
> > Hi Zhongpu,
> >
> > Thanks for the clarification. Prettier looks fine for formatting mk
&
Hi Jingson,
Thanks for sharing your thoughts. Please see my reply below.
On Thu, Feb 23, 2023 at 10:16 AM Jingsong Li wrote:
> Hi Jing Ge,
>
> First, flink-table-common contains all common classes of Flink Table,
> I think it is hard to bypass its dependence.
>
If any time wh
> > Thanks for the proposal.
> > > >
> > > > +1 for the proposal.
> > > >
> > > > I am confused about "Proposed TableEnvironment SQL API Changes", can
> > > > we just use catalog api for this requirement?
> > > >
>
md
> ```
>
> At last, it will never cause any conflict. Prettier is compatible with
> CommonMark (https://commonmark.org/) and GitHub Flavored Markdown.
>
>
> On 2023/02/22 10:22:46 Jing Ge wrote:
> > Hi Zhongpu,
> >
> > Thanks for starting this discussion. I was wondering
Hi Ran,
Thanks for driving the FLIP. It looks overall good. Would you like to add
a description of useLike and notLike? I guess useLike true is for "LIKE"
and notLike true is for "NOT LIKE" but I am not sure if I understood it
correctly. Furthermore, does it make sense to support "ILIKE" too?
Hi Zhongpu,
Thanks for starting this discussion. I was wondering how we could let every
contributor follow the same mk rule. I am not familiar with Prettier. Would
you like to help me understand some basic questions? Thanks.
Is there any way to integrate the format check into our CI pipeline?
congrats Sergey!
On Tue, Feb 21, 2023 at 1:15 PM Matthias Pohl
wrote:
> Congratulations, Sergey! Good job & well-deserved! :)
>
> On Tue, Feb 21, 2023 at 1:03 PM yuxia wrote:
>
> > Congratulations Sergey!
> >
> > Best regards,
> > Yuxia
> >
> > - 原始邮件 -
> > 发件人: "Martijn Visser"
> >
+ 1 for a new FLIP
It would be great if we could take this opportunity to go through all
current Flink SQL syntax and define a feasible classification in the FLIP.
In my opinion, the 4 categories, i.e. DDL, DML, DQL, DAL , used in Spark
doc [1] make sense.
We will then have a better big picture
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
401 - 500 of 718 matches
Mail list logo
