[IMPALA-9265] Add support for toolchain Kudu to provide maven artifacts

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Impala 3.4.0
• Fix Version/s: Impala 3.4.0
• Component/s: Infrastructure
• Labels: toolchain
• Epic Color: ghx-label-10
• Assignee: Attila Jeges
• Reporter: Joe McDonnell
• Created: 26/Dec/19 21:14
• Updated: 10/Feb/20 21:07
• Resolved: 28/Jan/20 16:20

Description

If toolchain Kudu provided Java artifacts, then toolchain Kudu could be used standalone without needing a separate Maven repository for Kudu artifacts. This is nice, because it would allow us to use toolchain Kudu for both USE_CDP_HIVE=true and USE_CDP_HIVE=false without any Java artifact version conflicts. Having only a single version of Kudu to build against would simplify Kudu/Impala integration projects.

To do this, the native toolchain (which may be a misnomer) would need to push Kudu artifacts to a repository. One option is for it to create a local filesystem repository and then include it in the kudu tarball produced.

Issue Links

• is related to: IMPALA-5490 Upgrade to GCC 7.x or greater