Thanks a lot for driving this release Xintong! Looking forward to the
1.11.3 release :-)
Cheers,
Till
On Tue, Dec 8, 2020 at 11:27 AM Xintong Song wrote:
> Hi devs,
>
> There has been a bit more delay but we finally get all bockers resolved.
>
> I'm creating the RC right now (commit id:
>
Hi devs,
There has been a bit more delay but we finally get all bockers resolved.
I'm creating the RC right now (commit id:
47c2d97499ed95a33c071e916eb8bde7b179e879).
This could take some time given that I'm doing this for the first time and
accessing to Apache Nexus Repository from my place is
Updates on the release progress.
- FLIP-27 is stabilizing on the master branch. Becket is working on the
final backportings, which is estimated to be finished this weekend.
- There's a new blocker FLINK-20442, a license problem discovered during
the 1.12.0 RC2 testings, which is already fixed for
Hi devs,
Updates on the release progress.
There are a couple of new blockers emerged since the last update, all of
which have been resolved in the past week.
The release 1.11.3 is still blocked on FLIP-27.
Stephan and Becket are trying to first get the feature stabilized on the
master branch
Thanks for the notice, Zhu.
Let's have the discussion on the jira ticket.
Thank you~
Xintong Song
On Mon, Nov 23, 2020 at 12:10 PM Zhu Zhu wrote:
> Hi Xintong,
> We just found an issue FLINK-20285 and I think it is a blocker for 1.11.3.
>
> Thanks,
> Zhu
>
> Gyula Fóra 于2020年11月18日周三
Hi Xintong,
We just found an issue FLINK-20285 and I think it is a blocker for 1.11.3.
Thanks,
Zhu
Gyula Fóra 于2020年11月18日周三 下午9:36写道：
> Hi All!
>
> I have found the following issue today which might be considered a blocker
> for this release as well:
>
>
Hi All!
I have found the following issue today which might be considered a blocker
for this release as well:
https://issues.apache.org/jira/browse/FLINK-20221
Could someone please quickly provide a second set of eyes and confirm that
this is indeed a big problem? :)
Thank you!
Gyula
On Wed,
Hi devs,
Updates on the progress of preparing the 1.11.3 release.
We are approaching the creation of our first release candidate. Thanks all
for the efforts so far.
# Ongoing threads
- *FLIP-27 backportings:* 74 out of 102 commits are already backported.
Stephan and Becket are actively
Thanks for the notice and fix, Roman.
Thank you~
Xintong Song
On Wed, Nov 11, 2020 at 5:53 PM Khachatryan Roman <
khachatryan.ro...@gmail.com> wrote:
> Hi,
>
> I'd like FLINK-20079 [1] to be merged into 1.11 and included in 1.11.3.
>
> [1] https://issues.apache.org/jira/browse/FLINK-20079
>
Hi,
I'd like FLINK-20079 [1] to be merged into 1.11 and included in 1.11.3.
[1] https://issues.apache.org/jira/browse/FLINK-20079
Regards,
Roman
On Tue, Nov 10, 2020 at 8:21 AM Xintong Song wrote:
> Thanks for the notice, Dian.
>
> Thank you~
>
> Xintong Song
>
>
>
> On Tue, Nov 10, 2020 at
Thanks for the notice, Dian.
Thank you~
Xintong Song
On Tue, Nov 10, 2020 at 10:19 AM Dian Fu wrote:
> Hi Xintong,
>
> I want to bring one more issue to your attention [1]. The test case
> UnalignedCheckpointCompatibilityITCase.test failed several times in the
> last nightly test of
Hi Xintong,
I want to bring one more issue to your attention [1]. The test case
UnalignedCheckpointCompatibilityITCase.test failed several times in the last
nightly test of release-1.11. We need to figure out if it's just an instable
test or caused by recent changes.
[1]
Thanks for the replies.
Thank you~
Xintong Song
On Tue, Nov 10, 2020 at 1:09 AM Becket Qin wrote:
> Hi Xintong,
>
> Thanks for driving the release. Just want to sync up on the FLIP-27
> backporting. Stephan and I are still trying to backport a bunch of patches
> of Source to 1.11.3.
Hi Xintong,
Thanks for driving the release. Just want to sync up on the FLIP-27
backporting. Stephan and I are still trying to backport a bunch of patches
of Source to 1.11.3. Including:
[FLINK-19698][connector/common] Add a close() method to the SplitReader.
[FLINK-19717]
Yes, I've downgraded FLINK-19816 to critical.
Cheers,
Till
On Mon, Nov 9, 2020 at 10:19 AM Xintong Song wrote:
> Thanks for the notice, Till.
>
> I just checked and found FLINK-20033 is already fixed. Shall we also
> downgrade FLINK-19816 to `Critical`?
>
> Thank you~
>
> Xintong Song
>
>
>
>
Thanks for the notice, Till.
I just checked and found FLINK-20033 is already fixed. Shall we also
downgrade FLINK-19816 to `Critical`?
Thank you~
Xintong Song
On Mon, Nov 9, 2020 at 4:42 PM Till Rohrmann wrote:
> I would like to bring one more critical issue to your attention which is
>
FLINK-20033 has been merged.
Cheers,
Till
On Mon, Nov 9, 2020 at 9:39 AM Till Rohrmann wrote:
> I would like to bring one more critical issue to your attention which is
> FLINK-20033 [1]. I believe that this issue is actually causing what has
> been reported in FLINK-19816 [2]. I hope to have
I would like to bring one more critical issue to your attention which is
FLINK-20033 [1]. I believe that this issue is actually causing what has
been reported in FLINK-19816 [2]. I hope to have it fixed by the end of
today. Once FLINK-20033 is fixed, I think that we don't have to block the
release
Hi devs,
I'd like to provide an update on the progress of preparing release 1.11.3.
*Blockers*
We currently have 3 remaining blockers. (3 resolved and 1 emerged compared
to last week)
- [FLINK-19698] Add close() method and onCheckpointComplete() to the Source.
The issue has been fixed on the
Thanks for the efforts so far with pushing for 1.11.3.
I'd like to provide a mid-week update on how we're looking with all the
pending blockers and backports:
*Blockers**:*
Currently all blockers either have an open PR, or have been merged. I'll
highlight below the blockers *that still require
> The collect() utils can be picked back, I see no issue with that (it is
isolated utilities).
Just checking on all the requested backports mentioned in this thread, and
figuring out which ones seem to still be unassigned / open.
Is someone working on backporting
@Stephan Ewen yeah, we can do that. don't worry about
it. your earlier email had the perfect explanation on why file source
shouldn't be backported.
On Tue, Nov 3, 2020 at 3:37 AM Stephan Ewen wrote:
> @Steven would it be possible to initially copy some of the code into the
> iceberg source
@Steven would it be possible to initially copy some of the code into the
iceberg source and later replace it by a dependency on the Flink file
source?
On Mon, Nov 2, 2020 at 8:33 PM Steven Wu wrote:
> Stephan, thanks a lot for explaining the file connector. that makes sense.
>
> I was asking
Stephan, thanks a lot for explaining the file connector. that makes sense.
I was asking because we were trying to reuse some of the implementations in
the file source for Iceberg source. Flink Iceberg source lives in the
Iceberg repo, which is not possible to code against the master branch of
the
Hi Steven!
So far there are no plans to pick back the file system connector code. This
is still evolving and not finalized for 1.12, so I don't feel it is a good
candidate to be backported.
However, with the base connector changes backported, you should be able to
run the file connector code from
Basically, it would be great to get the latest code in the
flink-connector-files (FLIP-27).
On Sat, Oct 31, 2020 at 9:57 AM Steven Wu wrote:
> Stephan, it will be great if we can also backport the DataStreamUtils
> related commits that help with collecting output from unbounded streams.
> e.g.
Stephan, it will be great if we can also backport the DataStreamUtils
related commits that help with collecting output from unbounded streams.
e.g.
https://github.com/apache/flink/commit/09a7a66b7313fea64817fe960a8da1265b428efc
I tried to copy and paste the code to unblock myself. but it quickly
I have started with backporting the source API changes. Some minor
conflicts to solve, will need a bit more to finish this.
On Fri, Oct 30, 2020 at 7:25 AM Tzu-Li (Gordon) Tai
wrote:
> @Stephan Ewen
> Are there already plans or ongoing efforts for backporting the list of
> FLIP-27 changes that
@Stephan Ewen
Are there already plans or ongoing efforts for backporting the list of
FLIP-27 changes that you posted?
On Thu, Oct 29, 2020 at 7:08 PM Xintong Song wrote:
> Hi folks,
>
> Just to provide some updates concerning the status on the
> test instabilities.
>
> Currently, we have 30
Hi folks,
Just to provide some updates concerning the status on the
test instabilities.
Currently, we have 30 unresolved tickets labeled with `Affects Version`
1.11.x.
+1 to backport the FLIP-27 adjustments to 1.11.x.
If possible, that would be great. Many people are looking forward to the
FLIP-27 interface, but they don't want to take the risk to upgrade to 1.12
(And wait 1.12). After all, 1.11 is a relatively stable version.
Best,
Jingsong
On Thu, Oct 29,
Thanks for starting this.
+1 form my side to backport the FLIP-27 adjustments to 1.11.x.
There were quite a few changes, and I think we need to cherry-pick them all
to not get some inconsistent mix of changes and many merge conflicts.
I made a list below of what we need to add to "release-1.11".
I would love to see this FLIP-27 source interface improvement [1] made to
1.11.3.
[1] https://issues.apache.org/jira/browse/FLINK-19698
On Wed, Oct 28, 2020 at 12:32 AM Tzu-Li (Gordon) Tai
wrote:
> Thanks for the replies so far!
>
> Just to provide a brief update on the status of blockers for
Thanks for the replies so far!
Just to provide a brief update on the status of blockers for 1.11.3 so far:
*PR opened, pending reviewer*- [FLINK-19717] SourceReaderBase.pollNext may
return END_OF_INPUT if SplitReader.fetch throws (
https://github.com/apache/flink/pull/13776)
*PR opened,
+1 for releasing Flink 1.11.3 as it contains a number of important
fixes and thanks Gordon and Xintong for volunteering.
Cheers,
Kostas
On Mon, Oct 26, 2020 at 4:37 AM Yu Li wrote:
>
> +1 for releasing Flink 1.11.3, and thanks Gordon and Xintong for
> volunteering as our release managers.
>
>
+1 for releasing Flink 1.11.3, and thanks Gordon and Xintong for
volunteering as our release managers.
Best Regards,
Yu
On Mon, 26 Oct 2020 at 09:45, Xintong Song wrote:
> Thanks Gordan for starting this discussion.
> My pleasure to help with the release process.
>
> Thank you~
>
> Xintong
Thanks Gordan for starting this discussion.
My pleasure to help with the release process.
Thank you~
Xintong Song
On Fri, Oct 23, 2020 at 11:29 PM Till Rohrmann wrote:
> Thanks for starting this discussion Gordon. There are over 100 issues
> which are fixed for 1.11.3. Hence +1 for a
Thanks for starting this discussion Gordon. There are over 100 issues which
are fixed for 1.11.3. Hence +1 for a soonish 1.11.3 release. Thanks for
volunteering as our release managers Gordon and Xintong!
Cheers,
Till
On Fri, Oct 23, 2020 at 5:02 PM Tzu-Li (Gordon) Tai
wrote:
> Hi,
>
> Xintong
Hi,
Xintong and I would like to start a discussion for releasing Flink 1.11.3
soon.
It seems like we already have a few pressing issues that needs to be
included in a new hotfix release:
- Heap-based timers’ restore behaviour is causing a critical recovery
issue for StateFun [1] [2] [3].
39 matches
Mail list logo
