Thanks Zhongqiang for driving this.
+1 for the proposal.
On Tue, Mar 26, 2024 at 1:36 PM Shawn Huang wrote:
> +1 for the proposal
>
> Best,
> Shawn Huang
>
>
> Hongshun Wang 于2024年3月26日周二 11:56写道：
>
> > +1 for the proposal
> >
> > Best Regards,
> > Hongshun Wang
> >
> > On Tue, Mar 26, 2024 at
+1 for the proposal
Best,
Shawn Huang
Hongshun Wang 于2024年3月26日周二 11:56写道：
> +1 for the proposal
>
> Best Regards,
> Hongshun Wang
>
> On Tue, Mar 26, 2024 at 11:37 AM gongzhongqiang >
> wrote:
>
> > Hi Martijn,
> >
> > Thank you for your feedback.
> >
> > I agree with your point that we
Du Yuzhou created FLINK-34935:
-
Summary: TIMESTAMP_LTZ type Unsupported when using JdbcCatalog to
read from Postgres
Key: FLINK-34935
URL: https://issues.apache.org/jira/browse/FLINK-34935
Project: Flink
+1 for the proposal
Best Regards,
Hongshun Wang
On Tue, Mar 26, 2024 at 11:37 AM gongzhongqiang
wrote:
> Hi Martijn,
>
> Thank you for your feedback.
>
> I agree with your point that we should make a one-time update to the menu,
> rather than continuously updating it. This will be done unless
Hi Martijn,
Thank you for your feedback.
I agree with your point that we should make a one-time update to the menu,
rather than continuously updating it. This will be done unless some
sub-projects are moved or archived.
Best regards,
Zhongqiang Gong
Martijn Visser 于2024年3月25日周一 23:35写道：
>
Hi, Timo
Thanks for your quick response, and your suggestion.
Yes, this discussion has turned into confirming whether it's a special
table or a special MV.
1. The key problem with MVs is that they don't support modification, so I
prefer it to be a special table. Although the periodic refresh
Hi devs,
I'm happy to announce that FLIP-433: State Access on DataStream API V2
[1] has been accepted with 9 approving votes (4 binding) [2]:
- Xintong Song (binding)
- Hangxiang Yu (binding)
- Rui Fan (binding)
- Gyula Fóra (binding)
- Zakelly Lan (non-binding)
- Jinzhong Li
Caican Cai created FLINK-34934:
--
Summary: Translation Flink-Kubernetes-Operator document framework
construction
Key: FLINK-34934
URL: https://issues.apache.org/jira/browse/FLINK-34934
Project: Flink
Thanks for joining, Ufuk & Robert :)
Best regards,
Weijie
Rui Fan <1996fan...@gmail.com> 于2024年3月25日周一 23:06写道：
> Welcome Ufuk and Robert join the release manager group!
>
> Best,
> Rui
>
> Márton Balassi 于2024年3月25日 周一20:04写道：
>
> > Thanks for kicking this off, folks.
> >
> > +1 for the
+1 (non-binding)
Best,
Yunfeng
On Wed, Mar 20, 2024 at 8:29 PM weijie guo wrote:
>
> Hi everyone,
>
>
> Thanks for all the feedback about the FLIP-433: State Access on
> DataStream API V2 [1]. The discussion thread is here [2].
>
>
> The vote will be open for at least 72 hours unless there is
Hi Timo,
> Please double check if this is implementable with the current stack. I
fear the parser or validator might not like the "identifier" argument?
I checked this, currently the validator throws an exception trying to get
the full qualifier name for `classifier_model`. But since
Hi Ahmed,
Looks like the feature freeze time for 1.20 release is June 15th. We can
definitely get the model DDL into 1.20. For predict and evaluate functions,
if we can't get into the 1.20 release, we can get them into the 1.21
release for sure.
Thanks,
Hao
On Mon, Mar 25, 2024 at 1:25 AM
Hi Ron,
Thank you so much for your reply!
1. I added the description to Motivation part of my document [1]
2. I suppose to inject this functionality to AbstractTopNFunction, thus it
will work for all its implementations. It doesn't depend of implementation
(either it would be
Matthias Pohl created FLINK-34933:
-
Summary:
JobMasterServiceLeadershipRunnerTest#testResultFutureCompletionOfOutdatedLeaderIsIgnored
isn't implemented properly
Key: FLINK-34933
URL:
Hi Zhongqiang Gong,
Are you suggesting to continuously update the menu based on the number of
releases, or just this one time? I wouldn't be in favor of continuously
updating: returning customers expect a certain order in the menu, and I
don't see a lot of value in continuously changing that. I
+1 for this proposal.
gongzhongqiang 于2024年3月25日周一 15:49写道：
> Hi everyone,
>
> I'd like to start a discussion on adjusting the Flink website [1] menu to
> improve accuracy and usability.While migrating Flink CDC documentation
> to the website, I found outdated links, need to review and update
Welcome Ufuk and Robert join the release manager group!
Best,
Rui
Márton Balassi 于2024年3月25日 周一20:04写道：
> Thanks for kicking this off, folks.
>
> +1 for the timeline and the release manager candidates (Weijie, Rui
> Fan,Ufuk/Robert).
>
> On Mon, Mar 25, 2024 at 12:54 PM Leonard Xu wrote:
>
> >
Thanks Zhongqiang for driving this discussion, +1 for the proposal
Best,
Rui
Jingsong Li 于2024年3月25日 周一22:47写道：
> +1 for the proposal
>
> On Mon, Mar 25, 2024 at 10:01 PM Ferenc Csaky
> wrote:
> >
> > Suggested changes makes sense, +1 for the proposed menus and order.
> >
> > Best,
> > Ferenc
+1 for the proposal
On Mon, Mar 25, 2024 at 10:01 PM Ferenc Csaky
wrote:
>
> Suggested changes makes sense, +1 for the proposed menus and order.
>
> Best,
> Ferenc
>
>
>
>
> On Monday, March 25th, 2024 at 14:50, Gyula Fóra wrote:
>
> >
> >
> > +1 for the proposal
> >
> > Gyula
> >
> > On Mon,
Caican Cai created FLINK-34932:
--
Summary: Translate concepts of Flink-Kubernetes-Operator
documentation
Key: FLINK-34932
URL: https://issues.apache.org/jira/browse/FLINK-34932
Project: Flink
Suggested changes makes sense, +1 for the proposed menus and order.
Best,
Ferenc
On Monday, March 25th, 2024 at 14:50, Gyula Fóra wrote:
>
>
> +1 for the proposal
>
> Gyula
>
> On Mon, Mar 25, 2024 at 12:49 PM Leonard Xu xbjt...@gmail.com wrote:
>
> > Thanks Zhongqiang for starting
+1 for the proposal
Gyula
On Mon, Mar 25, 2024 at 12:49 PM Leonard Xu wrote:
> Thanks Zhongqiang for starting this discussion, updating documentation
> menus according to sub-projects' activities makes sense to me.
>
> +1 for the proposed menus:
>
> > After:
> >
> > With Flink
> > With Flink
Ferenc Csaky created FLINK-34931:
Summary: Update Kudu connector DataStream Source/Sink
implementation
Key: FLINK-34931
URL: https://issues.apache.org/jira/browse/FLINK-34931
Project: Flink
Ferenc Csaky created FLINK-34930:
Summary: Move existing Kudu connector code from Bahir repo to
dedicated repo
Key: FLINK-34930
URL: https://issues.apache.org/jira/browse/FLINK-34930
Project: Flink
Ferenc Csaky created FLINK-34929:
Summary: Create "flink-connector-kudu" repository
Key: FLINK-34929
URL: https://issues.apache.org/jira/browse/FLINK-34929
Project: Flink
Issue Type:
Ferenc Csaky created FLINK-34928:
Summary: FLIP-439: Externalize Kudu Connector from Bahir
Key: FLINK-34928
URL: https://issues.apache.org/jira/browse/FLINK-34928
Project: Flink
Issue Type:
Hi everyone,
I'm happy to announce that FLIP-439: Externalize Kudu Connector from Bahir [1]
has been accepted with 12 approving votes, 6 of which are binding: [2]:
- Mate Czagany (non-binding)
- Gyula Fóra (binding)
- Gabor Somogyi (binding)
- Mátyás Őrhidi (binding)
- Hang Ruan (non-binding)
-
Thanks for kicking this off, folks.
+1 for the timeline and the release manager candidates (Weijie, Rui
Fan,Ufuk/Robert).
On Mon, Mar 25, 2024 at 12:54 PM Leonard Xu wrote:
> Wow, happy to see Ufuk and Robert join the release managers group.
>
> +1 for the release manager candidates(Weijie,
Thanks for joining, Ufuk & Robert. +1
Best,
Xintong
On Mon, Mar 25, 2024 at 7:54 PM Leonard Xu wrote:
> Wow, happy to see Ufuk and Robert join the release managers group.
>
> +1 for the release manager candidates(Weijie, Rui Fan,Ufuk and Robert)
> from my side.
>
>
> Best,
> Leonard
>
>
>
>
Wow, happy to see Ufuk and Robert join the release managers group.
+1 for the release manager candidates(Weijie, Rui Fan,Ufuk and Robert) from my
side.
Best,
Leonard
> 2024年3月25日 下午6:09，Robert Metzger 写道：
>
> Hi, thanks for starting the discussion.
>
> +1 for the proposed timeline and
Congratulations! Thanks Maximilian for the release work and all involved.
Best,
Leonard
> 2024年3月25日 下午7:04，Muhammet Orazov 写道：
>
> Great! Thanks Maximilian and everyone involved for the effort and release!
>
> Best,
> Muhammet
>
> On 2024-03-25 10:35, Maximilian Michels wrote:
>> The
Thanks Zhongqiang for starting this discussion, updating documentation menus
according to sub-projects' activities makes sense to me.
+1 for the proposed menus:
> After:
>
> With Flink
> With Flink Kubernetes Operator
> With Flink CDC
> With Flink ML
> With Flink Stateful Functions
>
Great! Thanks Maximilian and everyone involved for the effort and
release!
Best,
Muhammet
On 2024-03-25 10:35, Maximilian Michels wrote:
The Apache Flink community is very happy to announce the release of
the Apache Flink Kubernetes Operator version 1.8.0.
The Flink Kubernetes Operator
Congratulations! Thanks Max for the release and all involved for the great
work!
A gentle reminder to users: the maven artifact has just been released and
will take some time to complete.
Best,
Rui
On Mon, Mar 25, 2024 at 6:35 PM Maximilian Michels wrote:
> The Apache Flink community is very
After thinking about this more, this discussion boils down to whether
this is a special table or a special materialized view. In both cases,
we would need to add a special keyword:
Either
CREATE UPDATING TABLE
or
CREATE UPDATING MATERIALIZED VIEW
I still feel that the periodic refreshing
The Apache Flink community is very happy to announce the release of
the Apache Flink Kubernetes Operator version 1.8.0.
The Flink Kubernetes Operator allows users to manage their Apache
Flink applications on Kubernetes through all aspects of their
lifecycle.
Release highlights:
- Flink
Hi, thanks for starting the discussion.
+1 for the proposed timeline and the three proposed release managers.
I'm happy to join the release managers group as well, as a backup for Ufuk
(unless there are objections about the number of release managers)
On Mon, Mar 25, 2024 at 11:04 AM Ufuk
Hey all,
I'd like to join the release managers for 1.20 as well. I'm looking forward to
getting more actively involved again.
Cheers,
Ufuk
On Sun, Mar 24, 2024, at 11:27 AM, Ahmed Hamdy wrote:
> +1 for the proposed timeline and release managers.
> Best Regards
> Ahmed Hamdy
>
>
> On Fri, 22
Hi Di
Thank you for your patience and explanation.
If this is a server-side configuration, we currently cannot modify it in
the client configuration. If Doris supports client-side configuration in
the future, we can reconsider whether to support it.
I currently have no other questions regarding
Hi Ron and Lincoln,
thanks for the quick response and the very insightful discussion.
> we might limit future opportunities to optimize queries
> through automatic materialization rewriting by allowing data
> modifications, thus losing the potential for such optimizations.
This argument makes
Hi Jark and Hao,
thanks for the information, Jark! Great that the Calcite community
already fixed the problem for us. +1 to adopt the simplified syntax
asap. Maybe even before we upgrade Calcite (i.e. copy over classes), if
upgrading Calcite is too much work right now?
> Is `DESCRIPTOR` a
Hi, Roman
Thanks for your proposal, I intuitively feel that this optimization would
be very useful to reduce the amount of message amplification for TopN
operators. After briefly looking at your google docs, I have the following
questions:
1. Whether you can describe in detail the principle of
Hi everyone,
I'd like to start a discussion on adjusting the Flink website [1] menu to
improve accuracy and usability.While migrating Flink CDC documentation
to the website, I found outdated links, need to review and update menus
for the most relevant information for our users.
Proposal:
-
Hi, Feng
Yes, if the StreamLoad transaction timeout is very short, you may encounter
this situation.
The timeout for StreamLoad transactions is controlled by the
streaming_label_keep_max_second parameter [1] in FE (Frontend), and the default
value is 12 hours. Currently, it is a global
Hi,
Thanks for Lorenzo'reply and Zakelly's supplement.
@Lorenzo
> I think you got my question, and I did not realize that is not even allowed
> to modify some externally scoped variable in a lambda. I guess the point is
> that it is possible, but the user would really need to be willing to do
Hi, Ahmed
Thanks for your feedback.
Regarding your question:
> I want to iterate on Timo's comments regarding the confusion between
"Dynamic Table" and current Flink "Table". Should the refactoring of the
system happen in 2.0, should we rename it in this Flip ( as the suggestions
in the thread
46 matches
Mail list logo
