[
https://issues.apache.org/jira/browse/IMPALA-9279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035377#comment-17035377
]
ASF subversion and git services commented on IMPALA-9279:
---------------------------------------------------------
Commit 14ae6eae1e3e0ff78040ae2bad92d36d745cf365 in impala's branch
refs/heads/master from Attila Jeges
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=14ae6ea ]
IMPALA-9279: Update the Kudu version to include VARCHAR support
Before this change the preferred way of getting Kudu was to pull
it in from the specified CDH build (even if USE_CDP_HIVE was set
to true). Optionally by setting USE_CDH_KUDU to false, one could
force Impala to use the native toolchain Kudu. But even then, the
Kudu Java artifacts would be downloaded from CDH.
Since Kudu VARCHAR support won't be backported to CDH, this
behavior blocks the Impala side of the Kudu/Impala VARCHAR
integration.
With this change:
1. Using the native toolchain Kudu (including the Java artifacts)
is the default behavior. From now on USE_CDH_KUDU will be set
to false by default. Impala can be forced to fall back on
using the CDH Kudu by explicitly setting USE_CDH_KUDU to true.
2. Kudu version is updated to include the VARCHAR support.
Testing:
Ran exhaustive tests with USE_CDH_KUDU=true and
USE_CDH_KUDU=false.
Change-Id: Iafe56342d43cb63e35c0bbb1b4a99327dda0a44a
Reviewed-on: http://gerrit.cloudera.org:8080/15134
Reviewed-by: Attila Jeges <atti...@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
> Update the Kudu version to include VARCHAR support (and other functionality)
> ----------------------------------------------------------------------------
>
> Key: IMPALA-9279
> URL: https://issues.apache.org/jira/browse/IMPALA-9279
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 3.4.0
> Reporter: Joe McDonnell
> Assignee: Attila Jeges
> Priority: Critical
>
> There are several commits in progress that require Impala to use a more
> recent version of Kudu. Since the Kudu version in CDH build number is not
> recent, the current method of using Kudu from the CDH build number needs to
> change.
> In the long term, using Kudu from the CDP build number makes sense, once that
> supports all the platforms needed. That is tracked by IMPALA-8943.
> However, in the short term, it makes more sense to use Kudu from the native
> toolchain. This would apply for both USE_CDP_HIVE=true and
> USE_CDP_HIVE=false. This will require the native toolchain Kudu to provide
> maven artifacts. That is tracked by IMPALA-9265.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
