+1
Built on CentOS release 6.6 (Final) in release and debug modes.
Ran C++ tests for release build. All passed but few scenarios from
kudu-tool-test, which failed due to GLOG_colorlogtostderr set. Ran the
failed tests after unsetting GLOG_colorlogtostderr environment variable:
no failures.
As for the release notes, I think it would be nice to update those at
least including note about fix for KUDU-2443, if possible. I think it's
not a big deal, so even with current release for RC2 it looks good to me.
Thanks,
Alexey
On 6/5/18 5:21 PM, William Berkeley wrote:
+1
Built on el7.
Ran tests. Passed.
Put on a 4-node cluster with some existing data written by 1.5. Was able to
scan the data back (same results as before).
-Will
On Wed, May 30, 2018 at 8:24 PM, Grant Henke <[email protected]> wrote:
Thank you for all the validation Attila.
Good reminder on the release notes. I will update those. That doesn't
require a new release candidate.
Thank you,
Grant
On Wed, May 30, 2018 at 4:44 PM, Attila Bukor <[email protected]> wrote:
+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 it on this machine). Removing these two tests
allowed
all other tests to pass on the other Java projects.
* C++ release build fails on MacOS 10.13.2 with Apple LLVM version 9.1.0
(clang-902.0.39.1) build fails, but as MacOS support is experimental, I
believe this is not an issue and the build fails on 1.7.0 and 1.7.1-RC1
so
this is not a new regression. After backporting 61d3fff, the build
succeeds
and all tests pass. I cherry-picked this commit on branch-1.7.x in case
there will be a 1.7.2 or a 1.7.1-RC3.
* Java build on MacOS succeeds, all tests passed.
* Tested Maven repo, works fine.
* Skimmed through README, looks fine to me, but I'm not sure what to
check
here.
* Release notes hasn't been updated since RC1, I believe at least
KUDU-2443 and ColumnSchema.toString NPE fix should be mentioned, but I
also
think this doesn't warrant a new release candidate. I'm not sure about
the
policy on the release notes though.
Thanks for this RC, Grant!
Attila
On 2018. May 30., at 15:44, Grant Henke <[email protected]> wrote:
Hi,
The Apache Kudu team is happy to announce the first release candidate
for
Apache Kudu 1.7.1.
Apache Kudu 1.7.1 is a bug-fix release which fixes critical issues in
Kudu
1.7.0.
The is a source-only release. The artifacts have been staged here:
https://dist.apache.org/repos/dist/dev/kudu/1.7.1-RC2/
Java convenience binaries in the form of a Maven repository are staged
here:
https://repository.apache.org/content/repositories/orgapachekudu-1021/
It is tagged in Git as 1.7.1-RC1 and the corresponding git hash is the
following:
*https://git-wip-us.apache.org/repos/asf?p=kudu.git;a=commit;h=
5418bfcbbfc6c1809cc869e0119f003e8fb66e37
<https://git-wip-us.apache.org/repos/asf?p=kudu.git;a=commit;h=
5418bfcbbfc6c1809cc869e0119f003e8fb66e37>*
The release notes can be found here:
https://github.com/apache/kudu/blob/1.7.1-RC2/docs/release_notes.adoc
The KEYS file to verify the artifact signatures can be found here:
https://dist.apache.org/repos/dist/release/kudu/KEYS
I'd suggest going through the README and the release notes, building
Kudu,
and running the unit tests. Testing out the Maven repo would also be
appreciated.
The vote will run until Monday, June 4th at 11PM PDT.
Thank you,
Grant
--
Grant Henke
Software Engineer | Cloudera
[email protected] | twitter.com/gchenke | linkedin.com/in/granthenke
--
Grant Henke
Software Engineer | Cloudera
[email protected] | twitter.com/gchenke | linkedin.com/in/granthenke
