You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2020/01/07 02:33:00 UTC

[jira] [Assigned] (IMPALA-9265) Add support for toolchain Kudu to provide maven artifacts

     [ https://issues.apache.org/jira/browse/IMPALA-9265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe McDonnell reassigned IMPALA-9265:
-------------------------------------

    Assignee: Attila Jeges

> Add support for toolchain Kudu to provide maven artifacts
> ---------------------------------------------------------
>
>                 Key: IMPALA-9265
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9265
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: Impala 3.4.0
>            Reporter: Joe McDonnell
>            Assignee: Attila Jeges
>            Priority: Critical
>              Labels: toolchain
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org