Re: Kudu 1.16.0 Release Proposal

[Attila Bukor]

Hi,

I branched 1.16 yesterday, and opened a Google doc to compose the release notes
in the usual format: https://s.apache.org/kudu1.16rn

Please add your contributions that you think should be in the release notes.

I'll go through the commits made by the less regular contributors and add them.

Thanks,
Attila

Re: Kudu 1.16.0 Release Proposal

[Attila Bukor]

It’s been another month, there’s no new Log4J versions and our Java packages
have been updated. I’m planning to finally branch on Monday (2/7/2022).

Attila

Re: Kudu 1.16.0 Release Proposal

[Andrew Wong]

It seems like a worthwhile inclusion, and I think the patch is pretty well
formed already. I'll review it before the release.

On Wed, Dec 22, 2021 at 11:12 PM Yingchun Lai 
wrote:

> Would this patch [1] be a block for the release?
> This bug will cause the tables rebuilt by 'kudu master unsafe_rebuild'
> unable to alter schema.
>
> https://gerrit.cloudera.org/c/18112/
>
> Best regards,
> Yingchun Lai
>
>
> On Tue, Dec 21, 2021 at 3:25 AM Attila Bukor  wrote:
> >
> > Hi,
> >
> > Due to log4j CVEs being published or existing CVE scores getting bumped
> to >9
> > every few days, I was holding off on making this release, waiting until
> the dust
> > settles. Fortunately, it's not a big deal to us, but it can still
> potentially
> > impact our users in the Java/Spark clients or the Ranger subprocess.
> >
> > With the holidyas and the year end getting close, I decided to branch on
> 1/3,
> > assuming there's no new Log4J CVE that day.
> >
> > Attila
> >
>


-- 
Andrew Wong

Re: Kudu 1.16.0 Release Proposal

[Yingchun Lai]

Would this patch [1] be a block for the release?
This bug will cause the tables rebuilt by 'kudu master unsafe_rebuild'
unable to alter schema.

https://gerrit.cloudera.org/c/18112/

Best regards,
Yingchun Lai


On Tue, Dec 21, 2021 at 3:25 AM Attila Bukor  wrote:
>
> Hi,
>
> Due to log4j CVEs being published or existing CVE scores getting bumped to >9
> every few days, I was holding off on making this release, waiting until the 
> dust
> settles. Fortunately, it's not a big deal to us, but it can still potentially
> impact our users in the Java/Spark clients or the Ranger subprocess.
>
> With the holidyas and the year end getting close, I decided to branch on 1/3,
> assuming there's no new Log4J CVE that day.
>
> Attila
>

Re: Kudu 1.16.0 Release Proposal

[Attila Bukor]

Hi,

Due to log4j CVEs being published or existing CVE scores getting bumped to >9
every few days, I was holding off on making this release, waiting until the dust
settles. Fortunately, it's not a big deal to us, but it can still potentially
impact our users in the Java/Spark clients or the Ranger subprocess.

With the holidyas and the year end getting close, I decided to branch on 1/3,
assuming there's no new Log4J CVE that day.

Attila

Re: Kudu 1.16.0 Release Proposal

[Alexey Serbin]

Hi Attila,

Thank you very much for volunteering for 1.16.0 RM work!

So far I have nothing I'd like to squeeze into 1.16.0: I have some
scattered pieces of partition-related work I thought might be useful, but
the current state of the code looks good to go without those extras.  Also,
to enable the end-to-end functionality for that would require extra work on
the Impala side anyways, and I don't think it's viable to push those before
the end of this year.


Kind regards,

Alexey

On Thu, Dec 2, 2021 at 8:36 AM Attila Bukor  wrote:

> Hi,
>
> It’s been a while since our last release, so I’d like to volunteer to
> manage the release of Kudu 1.16.0.
>
> Please let me know if there’s any outstanding work you’d like to squeeze
> into this release. If there aren’t any, I’ll cut the branch on 12/10.
>
> Attila