You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kudu.apache.org by Attila Bukor <ab...@apache.org> on 2020/08/11 19:54:07 UTC
Re: Kudu 1.13
Hi,
To make sure we don't break backward and/or forward compatibility, I changed the
priority of KUDU-3176[1] to blocker and will fix it before I cut the release.
I'll also be out of office next week, so I propose to postpone the cutting of
the branch to 8/24 Monday.
If you know of any other outstanding bugs that we should consider as blockers,
please list them in this thread (and also change their priority on JIRA).
Also, please don't forget to list your significant changes for the release notes
in https://s.apache.org/kudu1.13rn
Thanks,
Attila
[1] https://issues.apache.org/jira/browse/KUDU-3176
On Thu, Jul 30, 2020 at 05:46:28PM +0200, Attila Bukor wrote:
> Hi Kudu devs,
>
> It's been almost 3 months since Kudu 1.12.0 has been released on 5/19, so I'd
> like to volunteer to RM Kudu 1.13.0.
>
> Based on previous experience, I'd like to have a window a bit longer than usual
> to allow finishing any in-progress work that you'd like to squeeze in to this
> release so I propose cutting the branch on 8/14 Friday. This will give us a
> little over two weeks.
>
> In turn, I'd like to get the release notes committed before we cut the RC1, this
> way it would actually be part of the release instead of available only online.
>
> Please collect your significant changes for the release notes in this document:
> https://s.apache.org/kudu1.13rn
>
> Thanks,
> Attila
Re: Kudu 1.13
Posted by Attila Bukor <ab...@apache.org>.
Hi Devs,
The 1.13.x branch has been cut yesterday at dcb9b71. I'm in the progress of
publishing an RC1, but if there's anything critical that needs to land in
1.13.0, please let me know and make sure to cherry pick it to branch-1.13.x.
Thanks,
Attila
On Tue, Sep 01, 2020 at 11:15:42PM +0200, Attila Bukor wrote:
> Hi,
>
> Thanks everyone for these patches, it seems all of these have been merged if I'm
> not missing anything. Please confirm if this is the case.
>
> I'm also trying to squeeze in a last minute improvement[1][2] that would make
> the ownership support more usable, but I should be able to merge it
> today/tomorrow if there are no other issues.
>
> Is there anything else I should wait for? If not, I'd like to cut the branch and
> start preparing RC1 tomorrow.
>
> Thanks,
> Attila
>
> On Tue, Aug 25, 2020 at 01:39:27PM -0700, Bankim Bhavsar wrote:
> > I would like Jim's Bloom filter change[1] that was merged yesterday night
> > (08/24) to be part of the 1.13 release
> > I don't see the branch for 1.13 upstream, so I'm assuming it's not cut yet.
> >
> > [1] https://gerrit.cloudera.org/c/16248/
> >
> > Thanks,
> > -Bankim.
> >
> >
> > On Tue, Aug 25, 2020 at 6:38 AM Grant Henke <gh...@cloudera.com.invalid>
> > wrote:
> >
> > > I would like to get in a few docker related changes.
> > > Primarily the ability to publish multi-arch images so that we can support
> > > ARM architectures via docker as well.
> > >
> > > These changes should be able to get in this week as well.
> > >
> > > Thanks,
> > > Grant
> > >
> > > On Mon, Aug 24, 2020 at 2:12 PM Alexey Serbin <aserbin@cloudera.com.invalid
> > > >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > I'd like to include the fix for KUDU-1587 [1] into the upcoming 1.13
> > > > release. With the fix for KUDU-2727 [2] already landed, KUDU-1587 might
> > > > become more pronounced . It's not about every workload, but rather about
> > > > some specific ones, of course. I think it's nice to have a way to
> > > mitigate
> > > > the issue if it appears in the fields after upgrading to 1.13.
> > > >
> > > > The change in the context of fixing KUDU-1587 consists of three patches
> > > > posted for review: [3], [4], [5]. I think it's realistic to expect those
> > > > patches to land this week, assuming I'm getting review feedback on those.
> > > > At least Andrew Wong already took a look at [4] (thank you Andrew!)
> > > >
> > > > [1] https://issues.apache.org/jira/browse/KUDU-1587
> > > > [2] https://issues.apache.org/jira/browse/KUDU-2727
> > > > [3] https://gerrit.cloudera.org/#/c/16312/
> > > > [4] https://gerrit.cloudera.org/#/c/16332/
> > > > [5] https://gerrit.cloudera.org/#/c/16343/
> > > >
> > > > Thanks!
> > > >
> > > >
> > > > Kind regards,
> > > >
> > > > Alexey
> > > >
> > > > On Tue, Aug 11, 2020 at 12:54 PM Attila Bukor <ab...@apache.org> wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > To make sure we don't break backward and/or forward compatibility, I
> > > > > changed the
> > > > > priority of KUDU-3176[1] to blocker and will fix it before I cut the
> > > > > release.
> > > > > I'll also be out of office next week, so I propose to postpone the
> > > > cutting
> > > > > of
> > > > > the branch to 8/24 Monday.
> > > > >
> > > > > If you know of any other outstanding bugs that we should consider as
> > > > > blockers,
> > > > > please list them in this thread (and also change their priority on
> > > JIRA).
> > > > >
> > > > > Also, please don't forget to list your significant changes for the
> > > > release
> > > > > notes
> > > > > in https://s.apache.org/kudu1.13rn
> > > > >
> > > > > Thanks,
> > > > > Attila
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/KUDU-3176
> > > > >
> > > > > On Thu, Jul 30, 2020 at 05:46:28PM +0200, Attila Bukor wrote:
> > > > > > Hi Kudu devs,
> > > > > >
> > > > > > It's been almost 3 months since Kudu 1.12.0 has been released on
> > > 5/19,
> > > > > so I'd
> > > > > > like to volunteer to RM Kudu 1.13.0.
> > > > > >
> > > > > > Based on previous experience, I'd like to have a window a bit longer
> > > > > than usual
> > > > > > to allow finishing any in-progress work that you'd like to squeeze in
> > > > to
> > > > > this
> > > > > > release so I propose cutting the branch on 8/14 Friday. This will
> > > give
> > > > > us a
> > > > > > little over two weeks.
> > > > > >
> > > > > > In turn, I'd like to get the release notes committed before we cut
> > > the
> > > > > RC1, this
> > > > > > way it would actually be part of the release instead of available
> > > only
> > > > > online.
> > > > > >
> > > > > > Please collect your significant changes for the release notes in this
> > > > > document:
> > > > > > https://s.apache.org/kudu1.13rn
> > > > > >
> > > > > > Thanks,
> > > > > > Attila
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Grant Henke
> > > Software Engineer | Cloudera
> > > grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
> > >
Re: Kudu 1.13
Posted by Attila Bukor <ab...@apache.org>.
Hi,
Thanks everyone for these patches, it seems all of these have been merged if I'm
not missing anything. Please confirm if this is the case.
I'm also trying to squeeze in a last minute improvement[1][2] that would make
the ownership support more usable, but I should be able to merge it
today/tomorrow if there are no other issues.
Is there anything else I should wait for? If not, I'd like to cut the branch and
start preparing RC1 tomorrow.
Thanks,
Attila
On Tue, Aug 25, 2020 at 01:39:27PM -0700, Bankim Bhavsar wrote:
> I would like Jim's Bloom filter change[1] that was merged yesterday night
> (08/24) to be part of the 1.13 release
> I don't see the branch for 1.13 upstream, so I'm assuming it's not cut yet.
>
> [1] https://gerrit.cloudera.org/c/16248/
>
> Thanks,
> -Bankim.
>
>
> On Tue, Aug 25, 2020 at 6:38 AM Grant Henke <gh...@cloudera.com.invalid>
> wrote:
>
> > I would like to get in a few docker related changes.
> > Primarily the ability to publish multi-arch images so that we can support
> > ARM architectures via docker as well.
> >
> > These changes should be able to get in this week as well.
> >
> > Thanks,
> > Grant
> >
> > On Mon, Aug 24, 2020 at 2:12 PM Alexey Serbin <aserbin@cloudera.com.invalid
> > >
> > wrote:
> >
> > > Hi,
> > >
> > > I'd like to include the fix for KUDU-1587 [1] into the upcoming 1.13
> > > release. With the fix for KUDU-2727 [2] already landed, KUDU-1587 might
> > > become more pronounced . It's not about every workload, but rather about
> > > some specific ones, of course. I think it's nice to have a way to
> > mitigate
> > > the issue if it appears in the fields after upgrading to 1.13.
> > >
> > > The change in the context of fixing KUDU-1587 consists of three patches
> > > posted for review: [3], [4], [5]. I think it's realistic to expect those
> > > patches to land this week, assuming I'm getting review feedback on those.
> > > At least Andrew Wong already took a look at [4] (thank you Andrew!)
> > >
> > > [1] https://issues.apache.org/jira/browse/KUDU-1587
> > > [2] https://issues.apache.org/jira/browse/KUDU-2727
> > > [3] https://gerrit.cloudera.org/#/c/16312/
> > > [4] https://gerrit.cloudera.org/#/c/16332/
> > > [5] https://gerrit.cloudera.org/#/c/16343/
> > >
> > > Thanks!
> > >
> > >
> > > Kind regards,
> > >
> > > Alexey
> > >
> > > On Tue, Aug 11, 2020 at 12:54 PM Attila Bukor <ab...@apache.org> wrote:
> > >
> > > > Hi,
> > > >
> > > > To make sure we don't break backward and/or forward compatibility, I
> > > > changed the
> > > > priority of KUDU-3176[1] to blocker and will fix it before I cut the
> > > > release.
> > > > I'll also be out of office next week, so I propose to postpone the
> > > cutting
> > > > of
> > > > the branch to 8/24 Monday.
> > > >
> > > > If you know of any other outstanding bugs that we should consider as
> > > > blockers,
> > > > please list them in this thread (and also change their priority on
> > JIRA).
> > > >
> > > > Also, please don't forget to list your significant changes for the
> > > release
> > > > notes
> > > > in https://s.apache.org/kudu1.13rn
> > > >
> > > > Thanks,
> > > > Attila
> > > >
> > > > [1] https://issues.apache.org/jira/browse/KUDU-3176
> > > >
> > > > On Thu, Jul 30, 2020 at 05:46:28PM +0200, Attila Bukor wrote:
> > > > > Hi Kudu devs,
> > > > >
> > > > > It's been almost 3 months since Kudu 1.12.0 has been released on
> > 5/19,
> > > > so I'd
> > > > > like to volunteer to RM Kudu 1.13.0.
> > > > >
> > > > > Based on previous experience, I'd like to have a window a bit longer
> > > > than usual
> > > > > to allow finishing any in-progress work that you'd like to squeeze in
> > > to
> > > > this
> > > > > release so I propose cutting the branch on 8/14 Friday. This will
> > give
> > > > us a
> > > > > little over two weeks.
> > > > >
> > > > > In turn, I'd like to get the release notes committed before we cut
> > the
> > > > RC1, this
> > > > > way it would actually be part of the release instead of available
> > only
> > > > online.
> > > > >
> > > > > Please collect your significant changes for the release notes in this
> > > > document:
> > > > > https://s.apache.org/kudu1.13rn
> > > > >
> > > > > Thanks,
> > > > > Attila
> > > >
> > > >
> > > >
> > >
> >
> >
> > --
> > Grant Henke
> > Software Engineer | Cloudera
> > grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
> >
Re: Kudu 1.13
Posted by Bankim Bhavsar <ba...@cloudera.com.INVALID>.
I would like Jim's Bloom filter change[1] that was merged yesterday night
(08/24) to be part of the 1.13 release
I don't see the branch for 1.13 upstream, so I'm assuming it's not cut yet.
[1] https://gerrit.cloudera.org/c/16248/
Thanks,
-Bankim.
On Tue, Aug 25, 2020 at 6:38 AM Grant Henke <gh...@cloudera.com.invalid>
wrote:
> I would like to get in a few docker related changes.
> Primarily the ability to publish multi-arch images so that we can support
> ARM architectures via docker as well.
>
> These changes should be able to get in this week as well.
>
> Thanks,
> Grant
>
> On Mon, Aug 24, 2020 at 2:12 PM Alexey Serbin <aserbin@cloudera.com.invalid
> >
> wrote:
>
> > Hi,
> >
> > I'd like to include the fix for KUDU-1587 [1] into the upcoming 1.13
> > release. With the fix for KUDU-2727 [2] already landed, KUDU-1587 might
> > become more pronounced . It's not about every workload, but rather about
> > some specific ones, of course. I think it's nice to have a way to
> mitigate
> > the issue if it appears in the fields after upgrading to 1.13.
> >
> > The change in the context of fixing KUDU-1587 consists of three patches
> > posted for review: [3], [4], [5]. I think it's realistic to expect those
> > patches to land this week, assuming I'm getting review feedback on those.
> > At least Andrew Wong already took a look at [4] (thank you Andrew!)
> >
> > [1] https://issues.apache.org/jira/browse/KUDU-1587
> > [2] https://issues.apache.org/jira/browse/KUDU-2727
> > [3] https://gerrit.cloudera.org/#/c/16312/
> > [4] https://gerrit.cloudera.org/#/c/16332/
> > [5] https://gerrit.cloudera.org/#/c/16343/
> >
> > Thanks!
> >
> >
> > Kind regards,
> >
> > Alexey
> >
> > On Tue, Aug 11, 2020 at 12:54 PM Attila Bukor <ab...@apache.org> wrote:
> >
> > > Hi,
> > >
> > > To make sure we don't break backward and/or forward compatibility, I
> > > changed the
> > > priority of KUDU-3176[1] to blocker and will fix it before I cut the
> > > release.
> > > I'll also be out of office next week, so I propose to postpone the
> > cutting
> > > of
> > > the branch to 8/24 Monday.
> > >
> > > If you know of any other outstanding bugs that we should consider as
> > > blockers,
> > > please list them in this thread (and also change their priority on
> JIRA).
> > >
> > > Also, please don't forget to list your significant changes for the
> > release
> > > notes
> > > in https://s.apache.org/kudu1.13rn
> > >
> > > Thanks,
> > > Attila
> > >
> > > [1] https://issues.apache.org/jira/browse/KUDU-3176
> > >
> > > On Thu, Jul 30, 2020 at 05:46:28PM +0200, Attila Bukor wrote:
> > > > Hi Kudu devs,
> > > >
> > > > It's been almost 3 months since Kudu 1.12.0 has been released on
> 5/19,
> > > so I'd
> > > > like to volunteer to RM Kudu 1.13.0.
> > > >
> > > > Based on previous experience, I'd like to have a window a bit longer
> > > than usual
> > > > to allow finishing any in-progress work that you'd like to squeeze in
> > to
> > > this
> > > > release so I propose cutting the branch on 8/14 Friday. This will
> give
> > > us a
> > > > little over two weeks.
> > > >
> > > > In turn, I'd like to get the release notes committed before we cut
> the
> > > RC1, this
> > > > way it would actually be part of the release instead of available
> only
> > > online.
> > > >
> > > > Please collect your significant changes for the release notes in this
> > > document:
> > > > https://s.apache.org/kudu1.13rn
> > > >
> > > > Thanks,
> > > > Attila
> > >
> > >
> > >
> >
>
>
> --
> Grant Henke
> Software Engineer | Cloudera
> grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
>
Re: Kudu 1.13
Posted by Grant Henke <gh...@cloudera.com.INVALID>.
I would like to get in a few docker related changes.
Primarily the ability to publish multi-arch images so that we can support
ARM architectures via docker as well.
These changes should be able to get in this week as well.
Thanks,
Grant
On Mon, Aug 24, 2020 at 2:12 PM Alexey Serbin <as...@cloudera.com.invalid>
wrote:
> Hi,
>
> I'd like to include the fix for KUDU-1587 [1] into the upcoming 1.13
> release. With the fix for KUDU-2727 [2] already landed, KUDU-1587 might
> become more pronounced . It's not about every workload, but rather about
> some specific ones, of course. I think it's nice to have a way to mitigate
> the issue if it appears in the fields after upgrading to 1.13.
>
> The change in the context of fixing KUDU-1587 consists of three patches
> posted for review: [3], [4], [5]. I think it's realistic to expect those
> patches to land this week, assuming I'm getting review feedback on those.
> At least Andrew Wong already took a look at [4] (thank you Andrew!)
>
> [1] https://issues.apache.org/jira/browse/KUDU-1587
> [2] https://issues.apache.org/jira/browse/KUDU-2727
> [3] https://gerrit.cloudera.org/#/c/16312/
> [4] https://gerrit.cloudera.org/#/c/16332/
> [5] https://gerrit.cloudera.org/#/c/16343/
>
> Thanks!
>
>
> Kind regards,
>
> Alexey
>
> On Tue, Aug 11, 2020 at 12:54 PM Attila Bukor <ab...@apache.org> wrote:
>
> > Hi,
> >
> > To make sure we don't break backward and/or forward compatibility, I
> > changed the
> > priority of KUDU-3176[1] to blocker and will fix it before I cut the
> > release.
> > I'll also be out of office next week, so I propose to postpone the
> cutting
> > of
> > the branch to 8/24 Monday.
> >
> > If you know of any other outstanding bugs that we should consider as
> > blockers,
> > please list them in this thread (and also change their priority on JIRA).
> >
> > Also, please don't forget to list your significant changes for the
> release
> > notes
> > in https://s.apache.org/kudu1.13rn
> >
> > Thanks,
> > Attila
> >
> > [1] https://issues.apache.org/jira/browse/KUDU-3176
> >
> > On Thu, Jul 30, 2020 at 05:46:28PM +0200, Attila Bukor wrote:
> > > Hi Kudu devs,
> > >
> > > It's been almost 3 months since Kudu 1.12.0 has been released on 5/19,
> > so I'd
> > > like to volunteer to RM Kudu 1.13.0.
> > >
> > > Based on previous experience, I'd like to have a window a bit longer
> > than usual
> > > to allow finishing any in-progress work that you'd like to squeeze in
> to
> > this
> > > release so I propose cutting the branch on 8/14 Friday. This will give
> > us a
> > > little over two weeks.
> > >
> > > In turn, I'd like to get the release notes committed before we cut the
> > RC1, this
> > > way it would actually be part of the release instead of available only
> > online.
> > >
> > > Please collect your significant changes for the release notes in this
> > document:
> > > https://s.apache.org/kudu1.13rn
> > >
> > > Thanks,
> > > Attila
> >
> >
> >
>
--
Grant Henke
Software Engineer | Cloudera
grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
Re: Kudu 1.13
Posted by Alexey Serbin <as...@cloudera.com.INVALID>.
Hi,
I'd like to include the fix for KUDU-1587 [1] into the upcoming 1.13
release. With the fix for KUDU-2727 [2] already landed, KUDU-1587 might
become more pronounced . It's not about every workload, but rather about
some specific ones, of course. I think it's nice to have a way to mitigate
the issue if it appears in the fields after upgrading to 1.13.
The change in the context of fixing KUDU-1587 consists of three patches
posted for review: [3], [4], [5]. I think it's realistic to expect those
patches to land this week, assuming I'm getting review feedback on those.
At least Andrew Wong already took a look at [4] (thank you Andrew!)
[1] https://issues.apache.org/jira/browse/KUDU-1587
[2] https://issues.apache.org/jira/browse/KUDU-2727
[3] https://gerrit.cloudera.org/#/c/16312/
[4] https://gerrit.cloudera.org/#/c/16332/
[5] https://gerrit.cloudera.org/#/c/16343/
Thanks!
Kind regards,
Alexey
On Tue, Aug 11, 2020 at 12:54 PM Attila Bukor <ab...@apache.org> wrote:
> Hi,
>
> To make sure we don't break backward and/or forward compatibility, I
> changed the
> priority of KUDU-3176[1] to blocker and will fix it before I cut the
> release.
> I'll also be out of office next week, so I propose to postpone the cutting
> of
> the branch to 8/24 Monday.
>
> If you know of any other outstanding bugs that we should consider as
> blockers,
> please list them in this thread (and also change their priority on JIRA).
>
> Also, please don't forget to list your significant changes for the release
> notes
> in https://s.apache.org/kudu1.13rn
>
> Thanks,
> Attila
>
> [1] https://issues.apache.org/jira/browse/KUDU-3176
>
> On Thu, Jul 30, 2020 at 05:46:28PM +0200, Attila Bukor wrote:
> > Hi Kudu devs,
> >
> > It's been almost 3 months since Kudu 1.12.0 has been released on 5/19,
> so I'd
> > like to volunteer to RM Kudu 1.13.0.
> >
> > Based on previous experience, I'd like to have a window a bit longer
> than usual
> > to allow finishing any in-progress work that you'd like to squeeze in to
> this
> > release so I propose cutting the branch on 8/14 Friday. This will give
> us a
> > little over two weeks.
> >
> > In turn, I'd like to get the release notes committed before we cut the
> RC1, this
> > way it would actually be part of the release instead of available only
> online.
> >
> > Please collect your significant changes for the release notes in this
> document:
> > https://s.apache.org/kudu1.13rn
> >
> > Thanks,
> > Attila
>
>
>