Manan Mangal created FLINK-32700:
Summary: Support job drain for Savepoint upgrade mode jobs in
Flink Operator
Key: FLINK-32700
URL: https://issues.apache.org/jira/browse/FLINK-32700
Project: Flink
+1
Best,
Ron
Jing Ge 于2023年7月26日周三 23:39写道：
> +1(binding).
>
> Theoretically, I agree with Matthias. But in the practices, afaic, those
> touched classes are low level APIs. We'd better have enough time to
> evaluate them with care. More time might be needed than we could have
> before the 1.18
Jacky Lau created FLINK-32699:
-
Summary: select typeof(proctime()); throw exception in sql-client
Key: FLINK-32699
URL: https://issues.apache.org/jira/browse/FLINK-32699
Project: Flink
Issue Type
Hi Timo,
Thanks for the FLIP, I also like the idea and option 3 sounds good to me.
I would like to discuss a case which is not mentioned in the current FLIP.
How are the "System column"s expressed in intermediate result, e.g. Join?
E.g. `SELECT * FROM t1 JOIN t2`, I guess it should not include "s
Ming Li created FLINK-32698:
---
Summary: Add getCheckpointOptions interface in
ManagedSnapshotContext
Key: FLINK-32698
URL: https://issues.apache.org/jira/browse/FLINK-32698
Project: Flink
Issue Typ
+ 1 (non-binding)
Thanks Xintong for driving this.
Best,
Jiabao
On 2023/07/20 09:22:46 Xintong Song wrote:
> Hi all,
>
> I'd like to start another round of VOTE for the must-have work items for
> release 2.0 [1]. The corresponding discussion thread is [2], and the
> previous voting thread is [
I'm actually thinking about supporting the LTS release until the next LTS
/ major version bump. E.g., if 1.19 is a LTS, we provide support for it
for the entire 2.x series, until we bump to 3.0 and make the last 2.x minor
release the new LTS. This probably will not require much more effort than
th
+1 binding
Thanks all for your work!
Best,
Jingsong
On Thu, Jul 27, 2023 at 10:52 AM Jark Wu wrote:
>
> +1 (binding)
>
> Thanks Xintong for driving this. Thanks all for finalizing the
> SourceFunction conclusion.
>
> Best,
> Jark
>
> On Wed, 26 Jul 2023 at 22:28, Alexander Fedulov
> wrote:
>
>
+1 (binding)
Thanks Xintong for driving this. Thanks all for finalizing the
SourceFunction conclusion.
Best,
Jark
On Wed, 26 Jul 2023 at 22:28, Alexander Fedulov
wrote:
> +1 (non-binding), assuming SourceFunction gets added back to the
> doc as a "nice-to-have". I am glad we've reached a conse
sunyanyong created FLINK-32697:
--
Summary: When using JDBC to insert data into the oracle database,
an error will be reported if the target field is lowercase,
Key: FLINK-32697
URL: https://issues.apache.org/jira/brow
I think we should add the release version when the FLIP is actually
released, in case of inconsistency.
Best,
Xintong
On Wed, Jul 26, 2023 at 9:48 PM Jing Ge wrote:
> +1 (binding)
>
> Please don't forget to update the release version to 2.0 in the FLIP.
>
> Best regards,
> Jing
>
> On Wed,
I'd be fine with either failing the request or fallback to null. But
fallback to 0 sounds surprising and against intuition to me.
Best,
Xintong
On Wed, Jul 26, 2023 at 7:44 PM Austin Cawley-Edwards <
austin.caw...@gmail.com> wrote:
> We discussed this in FLINK-29863[1] as well. While the JSO
Hi Matthias,
Thanks for your reply. Due to my busy work reasons, I would like to focus only
on
the `Path` class in FLIP-347 for now. As for the implementation of other
modules,
I will review them when I have available time later on.
Best regards,
Wencong Liu
At 2023-07-26 18:35:
Alexander Fedulov created FLINK-32696:
-
Summary: Promote Kinesis connector support to PublicEvolving
Key: FLINK-32696
URL: https://issues.apache.org/jira/browse/FLINK-32696
Project: Flink
Hi,
I split the blockers [1] from the nice-to-haves [2] and added some missing
items.
>From [1], the one about support for the ExternallyInducedSource [3] is
debatable -
AFAIK, it is only used by Pravega, which is not an officially-supported
connector.
This can, arguably, be something we could hop
Alexander Fedulov created FLINK-32695:
-
Summary: Migrate SourceFunction in Tests to Source API
Key: FLINK-32695
URL: https://issues.apache.org/jira/browse/FLINK-32695
Project: Flink
Issue
Alexander Fedulov created FLINK-32694:
-
Summary: Cascade deprecation to classes that implement
ParallelSourceFunction
Key: FLINK-32694
URL: https://issues.apache.org/jira/browse/FLINK-32694
Projec
Alexander Fedulov created FLINK-32693:
-
Summary: Cascade deprecation to classes that directly implement
SourceFunction
Key: FLINK-32693
URL: https://issues.apache.org/jira/browse/FLINK-32693
Proje
Alexander Fedulov created FLINK-32692:
-
Summary: [umbrella] Nice-to-haves for SourceFunction API removal
Key: FLINK-32692
URL: https://issues.apache.org/jira/browse/FLINK-32692
Project: Flink
Jim Hughes created FLINK-32691:
--
Summary: SELECT fcn does not work with an unset catalog or database
Key: FLINK-32691
URL: https://issues.apache.org/jira/browse/FLINK-32691
Project: Flink
Issue
Matyas Orhidi created FLINK-32690:
-
Summary: Report Double.NAN instead of null for missing autoscaler
metrics
Key: FLINK-32690
URL: https://issues.apache.org/jira/browse/FLINK-32690
Project: Flink
Hi
I agree with Konstantin that we should have a todo list to provide a clear
picture of when and how to deprecate the SinkFunction. Please let me check
if I can prepare a dedicated thread for it, since I got some feedback and
hints from previous discussions.
Best regards,
Jing
On Wed, Jul 26,
+1(binding).
Theoretically, I agree with Matthias. But in the practices, afaic, those
touched classes are low level APIs. We'd better have enough time to
evaluate them with care. More time might be needed than we could have
before the 1.18 release. A follow-up ticket might solve the concern. WDYT?
Hi,
There were many discussions wrt Source-/Sink-Function's deprecation.
Especially after FLIP-321 has been newly introduced. One reason, which
causes those discussions to happen back and forth, is that we have two
different understandings of how and when to use @deprecated.
This is the focus of
>
> @Mathias, I am not quite sure about the 3 versions description. Are you
> concerned that 1.x and 2.x LTS releases could overlap, if 3.0 comes early?
Yes. Maybe, that's only a theoretical scenario. It wouldn't work if we go
with your suggestion to use "proper time" rather than release cycles to
Timo Walther created FLINK-32689:
Summary: Insufficient validation for table.local-time-zone
Key: FLINK-32689
URL: https://issues.apache.org/jira/browse/FLINK-32689
Project: Flink
Issue Type:
+1 (non-binding), assuming SourceFunction gets added back to the
doc as a "nice-to-have". I am glad we've reached a consensus here.
Extra thanks to Leonard for coordinating this discussion in particular.
Best,
Alex
On Wed, 26 Jul 2023 at 15:43, Jing Ge wrote:
> +1 (non-binding), glad to see we
The question is if we want to tie the release cycle of 2.x to how much time
we give our users to migrate. And "time" is a critical word here. I can see
us
potentially wanting to iterate on the 2.x line more rapidly, because of all
of the
major changes, until the cycles get settled to a typical cade
Hi Jing,
> How could we help users and avoid this happening?
I don't think we will be able to avoid this in all cases. And I think
that's ok. Its always a trade-off between supporting new use cases and
moving the project forward and backwards compatibility (in a broad sense).
For example, we drop
+1 (binding)
Please don't forget to update the release version to 2.0 in the FLIP.
Best regards,
Jing
On Wed, Jul 26, 2023 at 5:49 PM Matthias Pohl
wrote:
> +1 (binding)
>
> On Wed, Jul 26, 2023 at 10:11 AM Yuxin Tan wrote:
>
> > +1 (non-binding)
> >
> > Best,
> > Yuxin
> >
> >
> > Xintong So
+1 (binding)
On Wed, Jul 26, 2023 at 4:21 PM weijie guo
wrote:
> +1 (binding)
>
> Best regards,
>
> Weijie
>
>
> Yuxin Tan 于2023年7月26日周三 16:11写道：
>
> > +1 (non-binding)
> >
> > Best,
> > Yuxin
> >
> >
> > Xintong Song 于2023年7月26日周三 16:09写道：
> >
> > > +1 (binding)
> > >
> > > Best,
> > >
> > >
+1 (non-binding), glad to see we are now on the same page. Thank you all.
Best regards,
Jing
On Wed, Jul 26, 2023 at 5:18 PM Yun Tang wrote:
> +1 (non-binding), thanks @xintong for driving this work.
>
>
> Best
> Yun Tang
>
> From: Zhu Zhu
> Sent: Wednesday, Ju
Matthias Pohl created FLINK-32688:
-
Summary: Remove deprecated exception history fields
Key: FLINK-32688
URL: https://issues.apache.org/jira/browse/FLINK-32688
Project: Flink
Issue Type: Sub-
Martijn Visser created FLINK-32687:
--
Summary: Performance regression on
handleGlobalFailureAndRestartAllTasks.BATCH_EVENLY since 2023-07-23
Key: FLINK-32687
URL: https://issues.apache.org/jira/browse/FLINK-32687
Martijn Visser created FLINK-32686:
--
Summary: Benchmark regression on startScheduling.BATCH and
startScheduling.STREAMING since 2023-07-24
Key: FLINK-32686
URL: https://issues.apache.org/jira/browse/FLINK-32686
Martijn Visser created FLINK-32685:
--
Summary: Benchmark regression on sortedMultiInput and
sortedTwoInput since 2023-07-18
Key: FLINK-32685
URL: https://issues.apache.org/jira/browse/FLINK-32685
Proj
Matthias Pohl created FLINK-32684:
-
Summary: Renaming AkkaOptions into PekkoOptions
Key: FLINK-32684
URL: https://issues.apache.org/jira/browse/FLINK-32684
Project: Flink
Issue Type: Technica
I think making the last minor release before a major release an LTS release
with extended support makes sense. I cannot think of a reason against the
four minor release cycles suggested by Marton. Only providing bug fixes and
not allowing features to be backported sounds reasonable to keep the
main
We discussed this in FLINK-29863[1] as well. While the JSON standard
doesn’t specify using null, the JavaScript standard encoding function
writes these values as null[2]. I think this will be least surprising to
users, and agree with the other points in this direction.
Best,
Austin
[1]: https://i
>
> Then we'd break the API for users that did already apply workarounds
> although the user hasn't done anything wrong.
That argument would also work against introducing the 0 default value. If
users have a workaround, introducing 0 might break their setup because they
might have used a different
Correct. I don't have the intention to block this FLIP if it's too much
effort to expand it. Sorry if that's the message that came across.
On Wed, Jul 26, 2023 at 12:17 PM Xintong Song wrote:
> I think it worth looking into all implementations of IOReadeableWritable.
> However, I would not consi
I think it worth looking into all implementations of IOReadeableWritable.
However, I would not consider that as a concern of this FLIP.
An important convention of the open-source community is volunteer work. If
Wencong only wants to work on the `Path` case, I think he should not be
asked to invest
+1 (binding)
On Wed, Jul 26, 2023 at 10:11 AM Yuxin Tan wrote:
> +1 (non-binding)
>
> Best,
> Yuxin
>
>
> Xintong Song 于2023年7月26日周三 16:08写道：
>
> > +1 (binding)
> >
> > Best,
> >
> > Xintong
> >
> >
> >
> > On Wed, Jul 26, 2023 at 3:35 PM Yuepeng Pan wrote:
> >
> > > +1 (non-binding)
> > >
> >
+1 (non-binding), thanks @xintong for driving this work.
Best
Yun Tang
From: Zhu Zhu
Sent: Wednesday, July 26, 2023 16:35
To: dev@flink.apache.org
Subject: Re: [VOTE] Release 2.0 must-have work items - Round 2
+1 (binding)
Thanks,
Zhu
Leonard Xu 于2023年7月26日周
Matthew de Detrich created FLINK-32683:
--
Summary: Update Pekko from 1.0.0 to 1.0.1
Key: FLINK-32683
URL: https://issues.apache.org/jira/browse/FLINK-32683
Project: Flink
Issue Type: Impr
Hi everyone,
The feature freeze of 1.18 has started now. That means that no new features
or improvements should now be merged into the master branch unless you ask
the release managers first, which has already been done for PRs, or pending
on CI to pass. Bug fixes and documentation PRs can still b
+1 (binding)
Thanks,
Zhu
Leonard Xu 于2023年7月26日周三 15:40写道：
>
> Thanks @xingtong for driving the work.
>
> +1(binding)
>
> Best,
> Leonard
>
> > On Jul 26, 2023, at 3:18 PM, Konstantin Knauf
> > wrote:
> >
> > Hi Xingtong,
> >
> > yes, I am fine with the conclusion for SourceFunction. I chatted
-0 (binding)
I'm not going to block this effort because it's still possible to cover
other occurrences in a subsequent FLIP if it's considered useful (I'm not
in the position to judge how important the IOReadableWritable interface is
in the context of removing the DataSet API).
The recent discuss
Dawid Wysakowicz created FLINK-32682:
Summary: Introduce option for choosing time function evaluation
methods
Key: FLINK-32682
URL: https://issues.apache.org/jira/browse/FLINK-32682
Project: Flink
+1 (binding)
Best regards,
Weijie
Yuxin Tan 于2023年7月26日周三 16:11写道：
> +1 (non-binding)
>
> Best,
> Yuxin
>
>
> Xintong Song 于2023年7月26日周三 16:09写道：
>
> > +1 (binding)
> >
> > Best,
> >
> > Xintong
> >
> >
> >
> > On Wed, Jul 26, 2023 at 2:26 PM Wencong Liu
> wrote:
> >
> > > Hi dev,
> > >
> >
+1 (binding)
Best regards,
Weijie
Yuxin Tan 于2023年7月26日周三 16:11写道：
> +1 (non-binding)
>
> Best,
> Yuxin
>
>
> Xintong Song 于2023年7月26日周三 16:09写道：
>
> > +1 (binding)
> >
> > Best,
> >
> > Xintong
> >
> >
> >
> > On Wed, Jul 26, 2023 at 2:29 PM Wencong Liu
> wrote:
> >
> > > Hi dev,
> > >
> >
Is the time constraint driven by the fact that you wanted to have that
effort being included in 1.18? If so, it looks like that's not possible
based on the decision being made for 1.18 to only allow document changes
[1]. So, there would be actually time to look into it. WDYT?
[1] https://lists.apa
+1 (non-binding)
Best,
Yuxin
Xintong Song 于2023年7月26日周三 16:09写道：
> +1 (binding)
>
> Best,
>
> Xintong
>
>
>
> On Wed, Jul 26, 2023 at 2:29 PM Wencong Liu wrote:
>
> > Hi dev,
> >
> >
> > I'd like to start a vote on FLIP-347.
> >
> >
> > Discussion thread:
> > https://lists.apache.org/thread/3
+1 (non-binding)
Best,
Yuxin
Xintong Song 于2023年7月26日周三 16:09写道：
> +1 (binding)
>
> Best,
>
> Xintong
>
>
>
> On Wed, Jul 26, 2023 at 2:26 PM Wencong Liu wrote:
>
> > Hi dev,
> >
> >
> > I'd like to start a vote on FLIP-344.
> >
> >
> > Discussion thread:
> > https://lists.apache.org/thread/5
+1 (non-binding)
Best,
Yuxin
Xintong Song 于2023年7月26日周三 16:08写道：
> +1 (binding)
>
> Best,
>
> Xintong
>
>
>
> On Wed, Jul 26, 2023 at 3:35 PM Yuepeng Pan wrote:
>
> > +1 (non-binding)
> >
> > Thanks.
> >
> > Yuepeng Pan.
> > At 2023-07-26 14:26:04, "Wencong Liu" wrote:
> > >Hi dev,
> > >
> >
+1 (binding)
Best,
Xintong
On Wed, Jul 26, 2023 at 2:29 PM Wencong Liu wrote:
> Hi dev,
>
>
> I'd like to start a vote on FLIP-347.
>
>
> Discussion thread:
> https://lists.apache.org/thread/3gcxhnqpsvb85golnlxf9tv5p43xkjgj
> FLIP:
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-347
+1 (binding)
Best,
Xintong
On Wed, Jul 26, 2023 at 2:26 PM Wencong Liu wrote:
> Hi dev,
>
>
> I'd like to start a vote on FLIP-344.
>
>
> Discussion thread:
> https://lists.apache.org/thread/5lyjrrdtwkngkol2t541r4xwoh7133km
> FLIP:
> https://cwiki.apache.org/confluence/pages/viewpage.action?
+1 (binding)
Best,
Xintong
On Wed, Jul 26, 2023 at 3:35 PM Yuepeng Pan wrote:
> +1 (non-binding)
>
> Thanks.
>
> Yuepeng Pan.
> At 2023-07-26 14:26:04, "Wencong Liu" wrote:
> >Hi dev,
> >
> >
> >I'd like to start a vote on FLIP-343.
> >
> >
> >Discussion thread:
> https://lists.apache.org/t
A side effect of the amount of deprecation FLIPs is that it takes up quite
a bit of time to verify them (if you want the community to do a proper
check). Individual FLIPs might not be that big. And of course, one could
argue that we can distribute the work to multiple people as a community
effort.
Hi Xintong,
It's fine to me to accept deprecations that only add annotations and
JavaDocs. We'll make a formal announcement later about 1.18 feature freeze
and plans on x-team testing, and please let us know (make a reply in that
thread) before you wanna do the deprecation action.
Best,
Qingsheng
Chesnay Schepler created FLINK-32681:
Summary:
RocksDBStateDownloaderTest.testMultiThreadCleanupOnFailure unstablie
Key: FLINK-32681
URL: https://issues.apache.org/jira/browse/FLINK-32681
Project:
Thanks @xingtong for driving the work.
+1(binding)
Best,
Leonard
> On Jul 26, 2023, at 3:18 PM, Konstantin Knauf
> wrote:
>
> Hi Xingtong,
>
> yes, I am fine with the conclusion for SourceFunction. I chatted with
> Leonard a bit last night. Let's continue this vote.
>
> Thanks for the clari
Lijie Wang created FLINK-32680:
--
Summary: Job vertex names get messed up once there is a source
vertex chained with a MultipleInput vertex in job graph
Key: FLINK-32680
URL: https://issues.apache.org/jira/browse/FLIN
+1 (non-binding)
Thanks.
Yuepeng Pan.
At 2023-07-26 14:26:04, "Wencong Liu" wrote:
>Hi dev,
>
>
>I'd like to start a vote on FLIP-343.
>
>
>Discussion thread:
>https://lists.apache.org/thread/zn11f460x70nn7f2ckqph41bvx416wxc
>FLIP:
>https://cwiki.apache.org/confluence/pages/viewpage.action?pa
Hi everyone,
I'd just like to add that we also said, that we would continue the
discussion to come up and agree on a list of concrete blockers for the
removal of SourceFunction, so that don't need to have the same discussion
again in half a year. And while we are add it, we should do the same thin
Hi Xingtong,
yes, I am fine with the conclusion for SourceFunction. I chatted with
Leonard a bit last night. Let's continue this vote.
Thanks for the clarification,
Konstantin
Am Mi., 26. Juli 2023 um 04:03 Uhr schrieb Xintong Song <
tonysong...@gmail.com>:
> Hi Konstantin,
>
> It seems the
66 matches
Mail list logo
