This has gone in now. You should be able to rebase, re-source
impala-config.sh, restart the minicluster (eg. with ./buildall.sh -noclean
-notests -start_minicluster), and continue working as normal.
If you rebase and fail to re-source impala-config.sh, you may see an error
like:
Traceback (most
The patch for this is finally out: https://gerrit.cloudera.org/#/c/11363/
I put some work into trying to make sure this will be as seamless as
possible for everyone.
- For people on Ubuntu 16 or the other CDH supported distros, you'll
automatically start using the CDH Kudu.
- For people on Ubuntu
So the toolchain binaries are provided for: centos5,6,7, debian7,8,
sles11,12, ubuntu14,16
The new CDH component binaries will be available for: redhat6,7, debian8,
sles12, ubuntu16
so we would be dropping easy support for building on basically centos5,
debian7, sles11, and ubuntu14
For people
Is there a path to building a version of Kudu locally for an arbitrary
linux distro?
Personally I am less concerned about 14.04 support and more concerned about
what the path to upgrading to 18.04. It would also be nice for it to be at
least possible to develop on RedHat-derived distros even if
+1 for simplifying Kudu updates.
I am also still on Ubuntu 14.04, but I am all for simplifying Kudu
integration:
I agree with Thomas that Kudu snapshots should be grouped with the other
CDH components.
Given that Ubuntu 14.04 will be EOL'd next spring, upgrading the
development OS
is a reasonably
I'm in favor of not spending developer time and effort to maintain
compatibility with 14.04. Personally I'm still developing on Ubuntu 14.04
so I'd be happy if we can support it without much pain. On the other hand
it EOLs in April 2019, so I might as well go to 18.04 now, should we decide
to drop
