Congrats Yuqi!
Hi Ke Deng,
I see you’re working on a patch, but I still can’t find the part about the WALs
in the design doc. Can you add it before working on the implementation?
Attila
smime.p7s
Description: S/MIME cryptographic signature
Congrats Abhishek, well deserved!
Apparently, I forgot to open the doc for comments, it is fixed now.
Hi All,
Manish opened a ticket today[1] to allow clients to connect to a cluster even if
it doesn't have the complete list of Masters.
This, I think, is important, but it could be a bit tricky to get it right and
might be a bit controversial.
I drafted a design doc[2] and added the motivation
>
> Data encryption at rest is a very important feature in 1.17, but there
> seems to be a lack of documents for users, how about squeezing
> documents about it into this release?
Thanks for the reminder, submitted the docs.
smime.p7s
Description: S/MIME cryptographic signature
Thanks for volunteering, Yingchun, I’m happy to help with the release, feel
free to DM me on Slack if you have any questions.
Hi,
Data at rest encryption is almost complete, and will soon be supported, so I've
been thinking about ways to avoid breaking it.
Right now, there are several unit and integration tests that enable encryption,
but the vast majority of the tests run with encryption disabled. There is a
+1
I was able to build and test this RC1 on CentOS 7.6 and 7.9 in release
mode with only two failures: master-test and tablet_server-test.
Unsetting KUDU_HOME, which is normally set in my .zshrc solved these
issues (web UI translation doesn't kick in this way), so this is also a
test-only bug.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Kudu devs!
The Apache Kudu team is happy to announce the first release candidate for Apache
Kudu 1.16.0.
Apache Kudu 1.16.0 is a minor release that offers many improvements and fixes
since Apache Kudu 1.15.0.
This is a source-only release.
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.
Hey,
I’ll restart Gerrit at 19:00 UTC time (in 7 minutes).
Attila
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
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
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
+1,
Verified the checksum and signature, built Kudu in release mode on CentOS 7, all
tests passed. Gradle build (including the tests) also succeeded on OpenJDK Java
8. Also ran the tests using the staged kudu-binary artifacts.
Attila
On Mon, Jan 25, 2021 at 04:18:53PM -0800, Alexey Serbin wrote:
Hi Kudu devs,
I've been working on a design for data at rest encryption in Kudu. I've shared
this with a few people already and gotten a decent amount of feedback and I
think it's ready to be shared with a broader audience. I'd appreciate any
feedback, comments, or suggestions.
You can find the
The Apache Kudu team is happy to announce the release of Kudu 1.13.0!
Kudu is an open source storage engine for structured data which supports
low-latency random access together with efficient analytical access
patterns. It is designed within the context of the Apache Hadoop ecosystem
and
:09:08PM +0200, Attila Bukor wrote:
> Hello Kudu devs!
>
> The Apache Kudu team is happy to announce the second release candidate for
> Apache Kudu 1.13.0.
>
> Apache Kudu 1.13.0 is a minor release that offers many improvements and fixes
> since Apache Kudu 1.12.0.
>
+1, I built it on CentOS 7 in release mode and ran all tests, including slow
ones. I also ran Java tests using the staged kudu-binary.
On Fri, Sep 11, 2020 at 11:09:08PM +0200, Attila Bukor wrote:
> Hello Kudu devs!
>
> The Apache Kudu team is happy to announce the second release
Hello Kudu devs!
The Apache Kudu team is happy to announce the second release candidate for
Apache Kudu 1.13.0.
Apache Kudu 1.13.0 is a minor release that offers many improvements and fixes
since Apache Kudu 1.12.0.
This is a source-only release. The artifacts have been staged here:
testHiveMetastoreIntegration
> - org.apache.kudu.test.cluster.TestKuduBinaryJarExtractor >
> testIsKuduBinaryJarOnClasspath
>
> On Mac OSX there were 133 test failures in Java tests.
>
> Greg
>
>
>
> On Sat, Sep 5, 2020 at 1:29 PM Attila Bukor wrote:
>
>
Hello Kudu devs!
The Apache Kudu team is happy to announce the first release candidate for Apache
Kudu 1.13.0.
Apache Kudu 1.13.0 is a minor release that offers many improvements and fixes
since Apache Kudu 1.12.0.
This is a source-only release. The artifacts have been staged here:
, 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 su
Gerrit has been restarted, it is online again.
Attila
On Thu, Sep 03, 2020 at 10:11:26AM +0200, Attila Bukor wrote:
> Hi,
>
> We're branching Kudu 1.13 and we need to restart gerrit.cloudera.org to update
> the configuration of the new branch. The planned downtime is a few minutes
&
Hi,
We're branching Kudu 1.13 and we need to restart gerrit.cloudera.org to update
the configuration of the new branch. The planned downtime is a few minutes
starting 11:50 AM CEST today.
I'll send another email when Gerrit is up again.
Attila
st 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://ge
/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 lo
Hi,
Recently I was looking for some release notes and found them on GitHub which got
me thinking. Now that we have a tighter integration between the official Gitbox
and the GitHub mirror, I think it would make sense to also post our release
notes and source artifacts to GitHub Releases page.
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
Hi Devs,
We put together a design doc[1] for support table ownership in Apache Kudu. If
you have any questions or comments regarding this feature please feel free to
comment on the doc or reply to this thread.
Attila
[1]
Hello everyone,
If you have an apache.org email, you should have received an email with an
invitation to take the 2020 ASF Community Survey. Please take 15 minutes to
complete it.
If you do not have an apache.org email address or you didn’t receive a link,
please follow this link to the
I’m +1 on this as well. It would be nice to be able to find the commit right
from the JIRA.
Sent from my iPhone
> On Nov 8, 2019, at 7:57 PM, Grant Henke wrote:
>
> +1 This would be great
>
>> On Fri, Nov 8, 2019 at 12:53 PM Andrew Wong wrote:
>>
>> SGTM. My first thought was that the
+1
- Successfully built in RELEASE mode on macOS Mojave and CentOS 7.3.
- Ran tests in slow mode on CentOS, memory_gc-itest seems to be flaky as it
failed at first but I re-ran it several times and it passed. There was another
failure which was environmental (address already in use).
-
I agree with Adar regarding the fix, we should avoid knowingly releasing a
version with an issue we can't fix down the road due to backwards-compatibility
issues.
I also agree with Alexey that we can revert the change introducing
live_row_count instead of waiting for the fix, at least if it takes
+1
Due to technical issues I didn't have the opportunity to build and test
it on a supported platform, but I was able to build it on MacOS in
release mode although a lot of the tests failed. I believe all of them
were platform-specific as most of them were HMS-related which I've seen
failing on
Sounds fair to me as well. I don't think the release notes are the right
place to document this though, maybe to known issues. Adding it to the
release notes would suggest it's a regression.
On Sat, Mar 02, 2019 at 12:03:34AM -0800, Andrew Wong wrote:
> Thank you all for participating thus far!
>
+1
I verified the checksum and the signature, then built Kudu from the RC2
tar on CentOS 7.6 both in debug and release build type, ran all tests in
slow mode. I also ran into KUDU-2718 and it does seem like a flaky test.
However, for me two other tests are failing consistently:
The following
+1
I ran all C++ tests with KUDU_ALLOW_SLOW_TESTS=1 both in DEBUG and
RELEASE on CentOS 7.6. master_hms-itest failed in both build types for
me, but as HMS integration is still not finished, I think that's fine -
plus it might be an environmental issue if it didn't fail for others.
I also ran
+1
On Tue, Jan 22, 2019 at 11:18:39PM -0800, Adar Lieber-Dembo wrote:
> +1
>
> Thanks for volunteering to RM, Andrew.
>
> On Tue, Jan 22, 2019 at 9:35 PM Andrew Wong wrote:
> >
> > Hello Kudu developers!
> >
> > It's been just around three months since we released 1.8.0. In that time,
> > we've
Hi,
The official kudu and kudu-site repos have been successfully migrated[1] from
git-wip-us.apache.org to gitbox.apache.org.
If you're not a committer and you've been using the GitHub mirror this change
shouldn't affect you at all.
If you're a committer or you've been using the git-wip-us.a.o
wer this seams like the way most
> Apache projects would go.
>
> On Thu, Jan 3, 2019 at 10:10 AM Attila Bukor wrote:
>
> > I'm 99% sure we don't. Gerrit uses it's own internal repo and doesn't
> > have a notiion of remotes without plugins (which we don't use as we
> &g
ra.org or
> jenkins.kudu.apache.org?
>
> On Thu, Jan 3, 2019 at 6:18 AM Attila Bukor wrote:
>
> > Hi,
> >
> > I submitted 2 patches to Gerrit to change our tooling to use the gitbox
> > URLs:
> >
> > - https://gerrit.cloudera.org/c/12150/
> > - https
Hi,
I submitted 2 patches to Gerrit to change our tooling to use the gitbox
URLs:
- https://gerrit.cloudera.org/c/12150/
- https://gerrit.cloudera.org/c/12151/
I'm not aware of any other changes we need to do, so if these patches
get +2s and there are no objections on this thread by Wednesday,
www.apache.org/dev/release-download-pages.html#closer>
>
> But there doesn't appear to be anything on
> https://www.apache.org/dist/kudu/1.8.0/
> <https://www.apache.org/dist/kudu/1.8.0/>
>
> Craig
>
> > On Oct 26, 2018, at 3:02 PM, Attila Bukor wrote:
>
escription or a link to a page with a
> > description of how to verify the download using the signature and checksum.
> >
> > If you can fix the download page timely, this announcement will be approved.
> >
> > Regards,
> >
> > Craig
> >
> >
>
ge with a
> description of how to verify the download using the signature and checksum.
>
> If you can fix the download page timely, this announcement will be approved.
>
> Regards,
>
> Craig
>
>
> From: Attila Bukor
> Subject: [ANNOUNCE] Apache Kudu 1.8.0 Rel
The Apache Kudu team is happy to announce the release of Kudu 1.8.0!
Kudu is an open source storage engine for structured data which supports
low-latency random access together with efficient analytical access
patterns. It is designed within the context of the Apache Hadoop ecosystem
and
all mirrors to be updated.
Attila
On Tue, Oct 16, 2018 at 11:47:21AM +0200, Attila Bukor wrote:
> Hi Devs,
>
> As suggested on the RC1 vote thread, I've included the complete fix for
> KUDU-2463 and created a new release candidate for Apache Kudu 1.8.0.
>
> Apache Kudu 1.8.0
Hi Devs,
As suggested on the RC1 vote thread, I've included the complete fix for
KUDU-2463 and created a new release candidate for Apache Kudu 1.8.0.
Apache Kudu 1.8.0 is a minor release that offers many improvements and
fixes
since the prior release.
The is a source-only release. The artifacts
Hi,
The Apache Kudu team is happy to announce the first release candidate for
Apache Kudu 1.8.0.
Apache Kudu 1.8.0 is a minor release that offers many improvements and fixes
since the prior release.
The is a source-only release. The artifacts have been staged here:
Hi Kudu devs,
As Andrew announced two weeks ago, we're preparing the release of Apache
Kudu 1.8.0. We originally planned to cut the branch on the 2nd of
October which was quickly pushed out to the 8th, which is today, but as
there are quite a few patches under review that are almost ready to be
Hi Devs,
I've created a Google doc to collect the release notes:
https://docs.google.com/document/d/1f6q9GyXNRNOaMra2AZ3pjS_shEYCP6EDbh3l8AA-8fw/edit?usp=sharing
Please add all bug fixes/improvements/features you worked on and think
it
should be included in the release notes.
Thanks,
Attila
Thanks Andrew, I'm just writing to confirm I'll manage the 1.8 release.
On Mon, Oct 01, 2018 at 11:37:57AM -0700, Andrew Wong wrote:
> One of our newest committers Attila (abukor) has volunteered to manage this
> release, so I'll hand off the 1.8 RM process to him. Thanks Attila!
>
> On Fri, Sep
Hi Everyone,
I've noticed that our infra is somewhat lacking in terms of security:
- http://kudu.apache.org doesn't redirect to https://kudu.apache.org
- https://jenkins.kudu.apache.org doesn't exist, even though secure information
is sent to this server (passwords)
The newest Chrome release
Hi Tim,
I’m not sure what you mean by relying on actual installations. If you have the
kudu, kudu-master and kudu-tserver binaries at the same location and they can
be executed, MiniKuduCluster can be used (“binDir” property should be set to
the directory containing the Kudu binaries). You
Hi TIm,
If you’re referring to MiniKuduCluster, it requires the Kudu binaries to start
a MiniCluster which in turn uses the actual kudu-master and kudu-tserver
binaries to set up a cluster, so it requires the Kudu binaries to be available
and will use separate processes, but you don’t have to
+1 (non-binding)
* Artifact's sha1 checksum and gpg signature is valid.
* C++ release build on el7 succeeded, all tests passed.
* Java build also succeeded on el7, 2 tests failed in kudu-client, both due to
environmental issues (stress tests maxed out fd count, don't have permissinos
to change
<t...@cloudera.com> wrote:
>
> Hm, that's interesting. KUDU-2379 is the only one I can think of that might
> have caused this issue. If you revert that change, does it fix the test?
>
> On Wed, May 9, 2018 at 11:46 AM, Attila Bukor <abu...@cloudera.com> wrote:
>
>> Hi Todd,
ore maintenance releases
> to address further bugs.
>
> Additionally my guess is this is a test-only issue since ITClientStress
> does some strange stuff reaching into Netty internals.
>
> -Todd
>
> On Wed, May 9, 2018 at 10:52 AM, Attila Bukor <abu...@cloudera.com> wrote
-1,
although still non-binding of course.
Attila
> On 2018. May 9., at 18:03, Attila Bukor <abu...@cloudera.com> wrote:
>
> +1 (non-binding)
>
> Built on CentOS 7.3 in release mode as well. I had one C++ test failure when
> I built this with Ninja due to it running "
+1 (non-binding)
Built on CentOS 7.3 in release mode as well. I had one C++ test failure when I
built this with Ninja due to it running "which ninja" and on this machine it's
called ninja-build. I was able to work around it by adding a symlink called
ninja to the $PATH, that way the actual
62 matches
Mail list logo
