+1(not-binding)
- verified signatures and hash
- reviewed the web PR
- checked the tag
- verified there are no binaries in the source archive
- built from sources
Best regards,
Jing
On Fri, Nov 24, 2023 at 4:07 AM weijie guo
wrote:
> Sorry, it's a non-binding vote. :)
>
> Best regards,
>
>
+1
Does it make sense to use 32.1.3-jre Guava?
Best regards,
Jing
On Thu, Nov 23, 2023 at 8:42 AM Yun Tang wrote:
> +1, thanks Sergey for driving this work.
>
> Best
> Yun Tang
>
> From: Leonard Xu
> Sent: Thursday, November 23, 2023 9:38
> To: dev
>
Jing Ge created FLINK-33624:
---
Summary: Bump Guava to 32.1.3-jre in flink-table
Key: FLINK-33624
URL: https://issues.apache.org/jira/browse/FLINK-33624
Project: Flink
Issue Type: Improvement
Thanks Piotr for driving it! Really like the idea of
supporting OpenTelemetry.
Best regards,
Jing
On Tue, Nov 21, 2023 at 6:20 PM Piotr Nowojski wrote:
> Thanks Roman. It kind of does depend, as the API is defined in the
> FLIP-384. But the voting thread for that FLIP has started, so I think
+1(binding)
Thanks!
Best Regards,
Jing
On Wed, Nov 22, 2023 at 11:21 AM Roman Khachatryan wrote:
> +1 (binding)
>
> Regards,
> Roman
>
> On Wed, Nov 22, 2023, 7:30 AM Hangxiang Yu wrote:
>
> > +1(binding)
> >
> > On Wed, Nov 22, 2023 at 10:29 AM Rui Fan <1996fan...@gmail.com> wrote:
> >
> > >
+1(binding) Thanks!
Best regards,
Jing
On Tue, Nov 21, 2023 at 6:17 PM Piotr Nowojski wrote:
> Hi All,
>
> I'd like to start a vote on the FLIP-384: Introduce TraceReporter and use
> it to create checkpointing and recovery traces [1]. The discussion thread
> is here [2].
>
> The vote will be
gt; Piotrek
>
>
> czw., 16 lis 2023 o 15:12 Roman Khachatryan napisał(a):
>
> > Thanks for the proposal,
> >
> > Starting with the minimal functionality and expanding if necessary as the
> > FLIP describes makes a lot of sense to me.
> >
> &g
any further thoughts.
>
> Best regards,
> Junrui
>
> Jing Ge 于2023年11月20日周一 05:46写道：
>
>> Hi Junrui,
>>
>> Thanks for bringing this to our attention. First of all, it makes sense
>> to deprecate RuntimeContext#getExecutionConfig.
>>
>> Afaic
Hi Junrui,
Thanks for bringing this to our attention. First of all, it makes sense to
deprecate RuntimeContext#getExecutionConfig.
Afaic, this is an issue of how we design API with clean concepts/aspects.
There are two issues mentioned in the FLIP:
1. short of user-facing abstraction - we just
+1(binding)
Thanks!
Best regards,
Jing
On Thu, Nov 16, 2023 at 8:46 AM Jark Wu wrote:
> +1 (binding)
>
> Best,
> Jark
>
> On Thu, 16 Nov 2023 at 12:41, Leonard Xu wrote:
>
> > +1(binding)
> >
> > Best,
> > Leonard
> >
> > > 2023年11月16日 下午12:13，Mingliang Liu 写道：
> > >
> > > +1 (non-binding)
>
Hi Piotr,
Sorry for the late reply and thanks for the proposal, it looks awesome!
In the discussion, you pointed out that it is difficult to build true
distributed traces. afaiu from FLIP-384 and FLIP-385, the
upcoming OpenTelemetry based TraceReporter will use the same Span
implementation and
one task
> fails,
> JobMaster doesn't update other tasks. If rest tasks report exceptions, they
> will
> increase the currentRestartAttempt.
>
> Detailed call stacks and code paths can be found in FLIP.
>
> Please let me know if my understanding is wrong or if it's not
+1 Thanks for the proposal!
Best regards,
Jing
On Tue, Nov 14, 2023 at 8:46 AM Mingliang Liu wrote:
> +1 on this effort.
>
> I opened a JIRA sometime ago on this topic [1] and Jagadesh submitted a PR
> [2] for review. In the comments, James proposed a different approach from
> the PR. I don't
Hi Rui,
Thanks for the proposal! I agree with Zhu that any changes of the default
behaviors will have impact on users' jobs in the production environment and
it would be necessary to have users' attention to to avoid
any surprises after upgrading Flink.
@Zhu
for 1, if we change the default
+1(binding)
Thanks!
Best Regards,
Jing
On Mon, Nov 13, 2023 at 8:34 AM Zhu Zhu wrote:
> +1 (binding)
>
> Thanks,
> Zhu
>
> Xia Sun 于2023年11月13日周一 15:02写道：
>
> > +1 (non-binding)
> >
> > Best,
> > Xia
> >
> > Samrat Deb 于2023年11月13日周一 12:37写道：
> >
> > > +1 (non binding)
> > >
> > > Bests,
> >
+1 since there are so many questions wrt PyFlink.
Best regards,
Jing
On Tue, Nov 7, 2023 at 2:23 AM Robin Moffatt
wrote:
> Since there have been no objections, can we go ahead and get this channel
> created please?
>
> thanks :)
>
> On Thu, 26 Oct 2023 at 16:00, Alexander Fedulov <
>
+1
Thanks for your effort!
Best regards,
Jing
On Mon, Nov 6, 2023 at 1:15 AM Konstantin Knauf wrote:
> Thank you for picking it up! +1
>
> Cheers,
>
> Konstantin
>
> Am Mo., 6. Nov. 2023 um 03:48 Uhr schrieb Yun Tang :
>
> > Hi all,
> >
> > I would like to discuss creating a new 1.17 patch
+1 for the final bug fix for Flink 1.16. Thanks for your effort!
Best regards,
Jing
On Mon, Nov 6, 2023 at 1:14 AM Konstantin Knauf wrote:
> +1. Thank you for picking it up. Yes, this will be the final bug fix for
> Flink 1.16.
>
> Am Mo., 6. Nov. 2023 um 03:47 Uhr schrieb Rui Fan
sses will be deprecated and which
> methods and fields will be deprecated. Please take a look at the updated
> version.
>
> Best regards,
> Junrui
>
> Jing Ge 于2023年11月5日周日 00:31写道：
>
> > Hi Junrui,
> >
> > Thanks for bringing the proposal to our attention. It looks overal
+1 (binding) Thanks!
Best regards,
Jing
On Mon, Nov 6, 2023 at 3:40 AM Timo Walther wrote:
> Hi everyone,
>
> I'd like to start a vote on FLIP-376: Add DISTRIBUTED BY clause[1] which
> has been discussed in this thread [2].
>
> The vote will be open for at least 72 hours unless there is an
Hi folks,
I started the same task and discussions in Feb. [1]. There were some
objections.
Best regards,
Jing
[1] https://issues.apache.org/jira/browse/FLINK-30862
On Wed, Nov 1, 2023 at 8:30 AM Junrui Lee wrote:
> Hi Zhanghao,
>
> Thank you for the proposal.
>
> +1 from my side. It would be
Hi folks,
Just like Matthias mentioned in his reply and Rui followed. Since 1.18.0
has been released, I'd suggest that we vote to make 1.16.3 the final bugix
release of 1.16, ask and wait for any objections. WDYT? Background info
could be found at [1].
Best regards,
Jing
[1]
Hi Junrui,
Thanks for bringing the proposal to our attention. It looks overall great.
I am just a little bit confused with the content of Flip with the following
questions:
1. How many complex java classes will be deprecated?
2. After reading the section title "Deprecate following classes,
TO n BUCKETS", we still include the
> >> bucketing terminology in the syntax for better understanding.
> >>
> >> If there are no other objections to this topic, I would still prefer to
> >> go with DISTRIBUTED BY.
> >>
> >> Regards,
> >&
uot; only refers to deciding between a list of partitioning
> strategies (namely hash and range partitioning) if the connector offers
> more than one.
>
> Regards,
> Timo
>
>
> On 30.10.23 12:39, Jing Ge wrote:
> > Hi Timo,
> >
> > The FLIP looks great! Thanks f
real issue though, and to help clear things up I
> think
> > > we should close FLINK-30238 in favor of a new ticket scoped to the
> specific
> > > PostCommitTopology problem.
> > >
> > > The other open concerns seem to mostly be around graduation criteria
Hi Danny,
+1 Thanks for driving it. Did you mean skip 4.1.1, since 4.1.0 has already
been released?
Best regards,
Jing
On Mon, Oct 30, 2023 at 11:49 AM Danny Cranmer
wrote:
> Hello all,
>
> I would like to start the discussion to release Apache Flink AWS connectors
> v4.2.0. We released
Hi Timo,
The FLIP looks great! Thanks for bringing it to our attention! In order to
make sure we are on the same page, I would ask some questions:
1. DISTRIBUTED BY reminds me DISTRIBUTE BY from Hive like Benchao mentioned
which is used to distribute rows amond reducers, i.e. focusing on the
Hi Lincoln,
Thanks for kicking off 1.19! I got a lot of experience as a release manager
for the 1.18 release. I would like to join you and participate in the 1.19
release cycle.
Best regards,
Jing
On Thu, Oct 26, 2023 at 6:27 PM Lincoln Lee wrote:
> Hi everyone,
>
> With the release
The Apache Flink community is very happy to announce the release of Apache
Flink 1.18.0, which is the first release for the Apache Flink 1.18 series.
Apache Flink® is an open-source unified stream and batch data processing
framework for distributed, high-performing, always-available, and accurate
Hi Ryan,
+1
Thanks for driving it. I have left one comment.
Best regards,
Jing
On Wed, Oct 25, 2023 at 10:05 PM David Radley
wrote:
> Looks good to me +1
>
> From: Ryan Skraba
> Date: Wednesday, 25 October 2023 at 17:19
> To: dev@flink.apache.org
> Subject: [EXTERNAL] [VOTE] Add JSON
Jing Ge created FLINK-33349:
---
Summary: CLONE - CLONE - Stage source and binary releases on
dist.apache.org
Key: FLINK-33349
URL: https://issues.apache.org/jira/browse/FLINK-33349
Project: Flink
Jing Ge created FLINK-33348:
---
Summary: CLONE - CLONE - Build and stage Java and Python artifacts
Key: FLINK-33348
URL: https://issues.apache.org/jira/browse/FLINK-33348
Project: Flink
Issue Type
Jing Ge created FLINK-33351:
---
Summary: CLONE - CLONE - Vote on the release candidate
Key: FLINK-33351
URL: https://issues.apache.org/jira/browse/FLINK-33351
Project: Flink
Issue Type: Sub-task
Jing Ge created FLINK-33350:
---
Summary: CLONE - CLONE - Propose a pull request for website updates
Key: FLINK-33350
URL: https://issues.apache.org/jira/browse/FLINK-33350
Project: Flink
Issue Type
Jing Ge created FLINK-33347:
---
Summary: CLONE - CLONE - Build Release Candidate: 1.18.0-rc3
Key: FLINK-33347
URL: https://issues.apache.org/jira/browse/FLINK-33347
Project: Flink
Issue Type: New
Hi David,
Thanks for picking this up. I was wondering if you have any concrete plan
like upgrading the FLIP or directly starting a new discussion with the
current FLIP as it is? Looking forward to having this connector.
Best regards,
Jing
On Tue, Oct 24, 2023 at 10:55 AM David Radley
wrote:
>
+1 (binding)
Thanks!
Best Regards,
Jing
On Thu, Oct 19, 2023 at 4:48 AM Dong Lin wrote:
> Thanks for the FLIP!
>
> +1 (binding)
>
> Xuannan Su 于2023年10月19日 周四10:30写道：
>
> > Hi all,
> >
> > We would like to start the vote for FLIP-329: Add operator attribute
> > to specify support for
Hi everyone,
I'm pleased to announce that we have unanimously approved this release
candidate:
There are 14 approving votes, 6 of which are binding:
- Cheng Pan (non-binding)
- Yun Tang (non-binding)
- Piotr Nowojski (binding)
- Matthias Pohl (binding)
- Martijn Visser (binding)
- Rui Fan
Hi David,
Please check [1] in the section Verify Java and Maven Version. Thanks!
Best regards,
Jing
[1]
https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release
On Mon, Oct 23, 2023 at 1:25 PM David Radley
wrote:
> Hi,
>
> I have an open pr in the backlog that improves the
Hi Zakelly,
Thank you for your effort! Really appreciate it!
Best regards,
Jing
On Thu, Oct 19, 2023 at 12:02 PM Yun Tang wrote:
> Thanks for Zakelly's great work!
>
>
> Best
> Yun Tang
>
> From: Piotr Nowojski
> Sent: Thursday, October 19, 2023 17:56
> To:
Hi everyone,
Please review and vote on the release candidate #3 for the version
1.18.0, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1],
, 2023 at 2:39 PM Matthias Pohl
wrote:
> Great catch, Yun Tang. I created FLINK-33291 [1] to cover the issue of
> enforcing the JDK (and Maven) version in the release profile.
>
> [1] https://issues.apache.org/jira/browse/FLINK-33291
>
> On Tue, Oct 17, 2023 at 1:28 PM Jing Ge
>
Jing Ge created FLINK-33301:
---
Summary: Add Java and Maven version checks in the bash script of
Flink release process
Key: FLINK-33301
URL: https://issues.apache.org/jira/browse/FLINK-33301
Project: Flink
ou update the new one.
>
>
> Best regards,
> Xianxun
>
> > 2023年10月18日 15:50，Jing Ge 写道：
> >
> > Hi Martijn,
> >
> > Fair enough! Thanks for sharing the reference!
> >
> > Best regards,
> > Jing
> >
> > On Wed, Oct 18, 2023 at 9
te on
> both of them at the same time.
>
> Best regards,
>
> Martijn
>
> [1] https://www.apache.org/legal/release-policy.html#release-approval
>
> On Wed, Oct 18, 2023 at 9:21 AM Jing Ge
> wrote:
> >
> > Hi Xianxun,
> >
> > Thanks for the feedbac
!
@xianxun Would you like to share the feedback asap? This will help us to
start RC3 vote at a fast pace. Thanks!
@Matthias Pohl @Martijn Visser
FYI, thanks again for your suggestions!
Best regards,
Jing
On Wed, Oct 18, 2023 at 9:20 AM Jing Ge wrote:
> Hi Xianxun,
>
> Thanks for the
gt; Thanks for the update, I checked the new maven repo, and the artifacts
> were built with JDK8 correctly.
> >
> >
> > Best
> > Yun Tang
> >
> > From: Jing Ge
> > Sent: Tuesday, October 17, 2023 23:31
> > To: d
epos/dist/dev/flink/flink-1.18.0-rc2/
> >
> > Best regards,
> > Xianxun
> >
> > > 2023年10月18日 10:24，Yun Tang 写道：
> > >
> > > Hi Jing,
> > >
> > > Thanks for the update, I checked the new maven repo, and the artifacts
> were built with
vs: please ignore this thread. I will start a new one as I
mentioned above.
Best regards,
Jing
[5] https://repository.apache.org/content/repositories/orgapacheflink-1659
On Tue, Oct 17, 2023 at 3:53 PM Jing Ge wrote:
> Hi Yun,
>
> Thanks for the feedback. Appreciate it! I will upda
...@aiven.io <
> sergey.nuyan...@aiven.io>
> Subject: Re: [VOTE] Release 1.18.0, release candidate #2
>
> Great catch, Yun Tang. I created FLINK-33291 [1] to cover the issue of
> enforcing the JDK (and Maven) version in the release profile.
>
> [1] https://issues.apache.or
> *Subject:* Re: [VOTE] Release 1.18.0, release candidate #2
> >
> > Great catch, Yun Tang. I created FLINK-33291 [1] to cover the issue of
> > enforcing the JDK (and Maven) version in the release profile.
> >
> > [1] https://issues.apache.org/jira/browse/FLINK-33291
k-1.18.0-rc2/flink-1.18.0-bin-scala_2.12.tgz>
[6] https://github.com/apache/flink/releases/tag/release-1.18.0-rc2
On Tue, Oct 17, 2023 at 12:27 PM Jing Ge wrote:
> Thanks Chesnay for the hint! Appreciate it!
>
>
Best regards,
> Jing
>
> On Tue, Oct 17, 2023 at 11:21 AM
+1
On Tue, Oct 17, 2023 at 11:13 AM Yong Fang wrote:
> +1
>
> On Tue, Oct 17, 2023 at 4:52 PM Leonard Xu wrote:
>
> > +1
> >
> >
> > > 2023年10月17日 下午4:50，Martijn Visser 写道：
> > >
> > > +1
> > >
> > > On Tue, Oct 17, 2023 at 10:34 AM Jingsong Li
> > wrote:
> > >>
> > >> Hi marton,
> > >>
> >
+1(binding)
Best regards,
Jing
On Tue, Oct 17, 2023 at 10:01 AM Yuepeng Pan wrote:
> +1 (non-binding)
>
> Best,Yuepeng Pan
>
>
> At 2023-10-17 15:51:59, "Yu Chen" wrote:
> >Hi all,
> >
> >Thank you to everyone for the feedback and detailed comments on
> FLIP-375[1].
> >Based on the discussion
t: Re: [VOTE] Release 1.18.0, release candidate #2
> >
> > +1 (non-binding)
> >
> > - Verified the signature and checksum
> > - Built from the source code
> > - Ran an example job on yarn cluster
> > - Checked the website PR
> >
> > Best,
>
From: Lijie Wang
> Sent: Tuesday, October 17, 2023 12:42
> To: dev@flink.apache.org
> Subject: Re: [VOTE] Release 1.18.0, release candidate #2
>
> +1 (non-binding)
>
> - Verified the signature and checksum
> - Built from the source code
> - Ran an example job on yarn c
e, as I am risk averse, I would suggest delaying this to v2 as
> Jing has proposed. This is a cleaner API, is there a demand for this in a
> dot version? If the community think this is too risk averse, then we could
> go with 1.19.
> > WDYT?
> >
> > Kind regards, David.
Congrats!
Best regards,
Jing
On Mon, Oct 16, 2023 at 10:33 AM Yuepeng Pan wrote:
> Congratulations, Ron!
>
> Best,
> Yuepeng PanAt 2023-10-16 09:56:56, "Jark Wu" wrote:
> >Hi, everyone
> >
> >On behalf of the PMC, I'm very happy to announce Ron Liu as a new Flink
> >Committer.
> >
> >Ron has
+1 (binding)
Best regards,
Jing
On Mon, Oct 16, 2023 at 9:16 AM Matt Wang wrote:
> +1 (non-binding)
>
>
> --
>
> Best,
> Matt Wang
>
>
> Replied Message
> | From | Zhu Zhu |
> | Date | 10/16/2023 15:12 |
> | To | |
> | Subject | Re: [VOTE] FLIP-366: Support standard YAML for FLINK
>
Congrats!
Best regards,
Jing
On Mon, Oct 16, 2023 at 10:33 AM Yuepeng Pan wrote:
> Congratulations, Jane !
>
>
>
> Best,
> Yuepeng Pan
>
> At 2023-10-16 09:58:02, "Jark Wu" wrote:
> >Hi, everyone
> >
> >On behalf of the PMC, I'm very happy to announce Jane Chan as a new Flink
> >Committer.
>
Hi everyone,
Please review and vote on the release candidate #2 for the version
1.18.0, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1],
Jing Ge created FLINK-33275:
---
Summary: CLONE - Vote on the release candidate
Key: FLINK-33275
URL: https://issues.apache.org/jira/browse/FLINK-33275
Project: Flink
Issue Type: Sub-task
Affects
Jing Ge created FLINK-33273:
---
Summary: CLONE - Stage source and binary releases on
dist.apache.org
Key: FLINK-33273
URL: https://issues.apache.org/jira/browse/FLINK-33273
Project: Flink
Issue
Jing Ge created FLINK-33274:
---
Summary: CLONE - Propose a pull request for website updates
Key: FLINK-33274
URL: https://issues.apache.org/jira/browse/FLINK-33274
Project: Flink
Issue Type: Sub
Jing Ge created FLINK-33271:
---
Summary: CLONE - Build Release Candidate: 1.18.0-rc2
Key: FLINK-33271
URL: https://issues.apache.org/jira/browse/FLINK-33271
Project: Flink
Issue Type: New Feature
Jing Ge created FLINK-33272:
---
Summary: CLONE - Build and stage Java and Python artifacts
Key: FLINK-33272
URL: https://issues.apache.org/jira/browse/FLINK-33272
Project: Flink
Issue Type: Sub-task
t; > > do you think?
> > > >
> > > >
> > > >
> > > > Kind regards, David.
> > > >
> > > >
> > > > From: Zakelly Lan
> > > > Date: Monday, 9 October 2023 at 18:12
> > > > To: de
+1(binding) Thanks!
Best regards,
Jing
On Wed, Oct 11, 2023 at 9:34 AM Yuepeng Pan wrote:
> +1(non-binding)
> Thanks for your driving the voting thread.
>
> Best Regards.
> Yuepeng Pan
>
> On 2023/10/06 16:33:40 Joao Boto wrote:
> > Hi all, Thank you to everyone for the feedback on
+1(binding)
Best Regards,
Jing
On Wed, Oct 11, 2023 at 5:36 AM Zakelly Lan wrote:
> +1(non-binding)
>
> Thanks for driving this.
>
> Best,
> Zakelly
>
> On Wed, Oct 11, 2023 at 11:22 AM Weihua Hu wrote:
> >
> > +1(binding)
> >
> > Best,
> > Weihua
> >
> >
> > On Wed, Oct 11, 2023 at 10:56 AM
Hi everyone,
The RC2 for Apache Flink 1.18.0 has been created. The related voting
process will be triggered once the announcement is ready. The RC2 has all
the artifacts that we would typically have for a release, except for the
release note and the website pull request for the release
; [4] https://issues.apache.org/jira/browse/FLINK-33186
> [5] https://issues.apache.org/jira/browse/FLINK-32996
> [6] https://issues.apache.org/jira/browse/FLINK-32907
>
>
> On Mon, Oct 9, 2023 at 10:06 AM Jing Ge
> wrote:
>
> > Hi Folks,
> >
> > Verve
>
> [1] https://github.com/async-profiler/async-profiler/issues/14
>
> Best
> Yun Tang
>
>
> From: Jing Ge
> Sent: Tuesday, October 10, 2023 12:05
> To: dev@flink.apache.org
> Subject: Re: [DISCUSS] FLIP-375: Built-in cross-plat
+1 for the s3 file consolidation. We already have many issues with internal
communication and talking to customers. Different file schemas are not very
user friendly, btw.
Best regards,
Jing
On Mon, Oct 9, 2023 at 6:49 PM Matthias Pohl
wrote:
> I would agree with David's proposal as well.
>
>
the user to download the results of the corresponding
> files on taskmanager with the blob service.
>
> Are all process-level flamegraphs stored at BlobStore?
> Are they maintained by JobManager after sampling?
> Is there cleanup strategy? Or max-save-count strategy?
>
> Best,
>
Hi Yu, Hi Yun,
Brilliant idea! People are keen to use it. Thanks for your proposal! I was
wondering:
1. will it replace the current flame graph, i.e. the current flame graph
will be deprecated and removed?
2. does it make sense to provide the performance difference between enable
and disable it?
+1 good idea! Looking forward to Flink OLAP!
Best regards,
Jing
On Sat, Oct 7, 2023 at 1:36 PM Yangze Guo wrote:
> Thanks for all your comments.
>
> @Rui
> Thanks for the reminder. The "env.java.opts.all" has already taken effect
> now.
>
>
> Best,
> Yangze Guo
>
> On Sat, Oct 7, 2023 at 6:45
+1(binding)
Best Regards,
Jing
On Mon, Oct 9, 2023 at 10:40 AM Ahmed Hamdy wrote:
> +1 (non-binding)
> Best Regards
> Ahmed Hamdy
>
>
> On Mon, 9 Oct 2023 at 09:38, xiangyu feng wrote:
>
> > +1 (non-binding)
> >
> > Feng Jin 于2023年10月9日周一 16:00写道：
> >
> > > +1 (non-binding)
> > >
> > > Best,
Jing Ge created FLINK-33216:
---
Summary: turn off the public access of the s3 bucket flink-nightly
Key: FLINK-33216
URL: https://issues.apache.org/jira/browse/FLINK-33216
Project: Flink
Issue Type
Jing Ge created FLINK-33215:
---
Summary: [Umbrella] use https://nightlies.apache.org/flink/ as the
flink artifact server for connector nightly build
Key: FLINK-33215
URL: https://issues.apache.org/jira/browse/FLINK
Hi Folks,
Ververica has made the files publicly accessible. Could anyone check if any
connector build works again?
Best regards,
Jing
On Mon, Oct 9, 2023 at 9:07 AM Jing Ge wrote:
> Hi Sergey and devs,
>
> Thanks for bringing this to our attention. I am open to discuss that.
gt; > > * Verified pom file versions
> > >> > > * Went over NOTICE file/pom files changes without finding anything
> > >> > > suspicious
> > >> > > * Deployed standalone session cluster and ran WordCount example in
> &
sums GPG signatures
> > >> > > * Compared checkout with provided sources
> > >> > > * Verified pom file versions
> > >> > > * Went over NOTICE file/pom files changes without finding anything
> > >> > > suspicious
> >
Jing Ge created FLINK-33195:
---
Summary: ElasticSearch Connector should directly depend on
3rd-party libs instead of flink-shaded repo
Key: FLINK-33195
URL: https://issues.apache.org/jira/browse/FLINK-33195
e system more complicated to operate.
>
> I think my proposal to support both THROW and IGNORE semantics should
> satisfy both mine requirements and your concerns, so to be honest I am
> disappointed that you don't want to reach a compromise, but you just
> block the effort.
>
> B
ng loaded in their own classloader. That still is the north
> star and the only reasonable way to ensure that multiple connectors can
> be safely used with SQL.
>
> On 02/10/2023 18:32, Jing Ge wrote:
> > Hi Sergey,
> >
> > Thanks for sharing your thoughts. It could some
Jing Ge created FLINK-33194:
---
Summary: AWS Connector should directly depend on 3rd-party libs
instead of flink-shaded repo
Key: FLINK-33194
URL: https://issues.apache.org/jira/browse/FLINK-33194
Project
Jing Ge created FLINK-33193:
---
Summary: JDBC Connector should directly depend on 3rd-party libs
instead of flink-shaded repo
Key: FLINK-33193
URL: https://issues.apache.org/jira/browse/FLINK-33193
Project
Jing Ge created FLINK-33191:
---
Summary: Kafka Connector should directly depend on 3rd-party libs
instead of flink-shaded repo
Key: FLINK-33191
URL: https://issues.apache.org/jira/browse/FLINK-33191
Project
Jing Ge created FLINK-33190:
---
Summary: Externalized Connectors should directly depend on
3rd-party libs instead of shaded repo
Key: FLINK-33190
URL: https://issues.apache.org/jira/browse/FLINK-33190
t; >
> > IGNORED: ignore hints
> >
> > Are you two fine with that option @Jing @Sergey?
> >
> > Since this thread had a few misunderstandings already, I'd suggest to
> > convert it to a FLIP and follow with a VOTE shortly. @Bonnie would you
> > like to h
and
> https://issues.apache.org/jira/browse/FLINK-33017 are resolved before
> releasing 1.18?
>
> Kind regards, David.
>
>
> From: Jing Ge
> Date: Wednesday, 27 September 2023 at 15:11
> To: dev@flink.apache.org
> Subject: [EXTERNAL] Re: [ANNOUNCE] Release 1.18.0,
d
>
> looking forward to seeing other opinions about that
>
> On Wed, Sep 13, 2023 at 9:47 PM Jing Ge
> wrote:
>
> > Hi Sergey,
> >
> > Thanks for doing the analysis and providing the great insight. I did my
> own
> > analysis and got the same conclus
ration options into a specific category, e.g.
> so
> > >> that
> > >> > > you
> > >> > > > > can have a default Flink without any hardening, a read-only
> > >> Flink, a
> > >> > > > > fully-hardened Flink etc)
> > >> > > >
Hi everyone,
The RC1 for Apache Flink 1.18.0 has been created. The related voting
process will be triggered once the announcement is ready. The RC1 has all
the artifacts that we would typically have for a release, except for the
release note and the website pull request for the release
an existing job to use this feature:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=263429150
> .
>
> Best,
> Zhanghao Chen
> ________
> 发件人: Jing Ge
> 发送时间: 2023年9月25日 23:02
> 收件人: dev@flink.apache.org
> 主题: Re: [DISCUSS] FLIP-3
Hi Folks,
@Ryan FYI: CI passed and the PR has been merged. Thanks!
If there are no more other concerns, I will start publishing 1.18-rc1.
Best regards,
Jing
On Mon, Sep 25, 2023 at 1:40 PM Jing Ge wrote:
> Hi Ryan,
>
> Thanks for reaching out. It is fine to include it but we nee
a to 1.1.10.4"
>
>
>
> On Mon, Sep 25, 2023 at 3:54 PM Jing Ge
> wrote:
> >
> > Thanks Zakelly for the update! Appreciate it!
> >
> > @Piotr Nowojski If you do not have any other
> > concerns, I will move forward to create 1.18 rc1 and start votin
+1(binding) Thanks!
Best regards,
Jing
On Mon, Sep 25, 2023 at 3:48 AM Chen Zhanghao
wrote:
> Thanks for driving this. +1 (non-binding)
>
> Best,
> Zhanghao Chen
>
> 发件人: xiangyu feng
> 发送时间: 2023年9月25日 17:38
> 收件人: dev@flink.apache.org
> 主题: [VOTE] FLIP-362:
+1(binding) Thanks!
Best Regards,
Jing
On Sun, Sep 24, 2023 at 10:30 PM Shammon FY wrote:
> Hi devs,
>
> Thanks for all the feedback on FLIP-314: Support Customized Job Lineage
> Listener [1] in thread [2].
>
> I would like to start a vote for it. The vote will be opened for at least
> 72
101 - 200 of 718 matches
Mail list logo
