[ 
https://issues.apache.org/jira/browse/IMPALA-7871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16692454#comment-16692454
 ] 

ASF subversion and git services commented on IMPALA-7871:
---------------------------------------------------------

Commit 70fbd1df446f4830b55d684d82c851867b9c1444 in impala's branch 
refs/heads/master from [~joemcdonnell]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=70fbd1d ]

IMPALA-7871: Don't load Hive builtins

Dataload has a step of "Loading Hive builtins" that
loads a bunch of jars into HDFS/S3/etc. Despite
its name, nothing seems to be using these.
Dataload and core tests succeed without this step.

This removes the Hive builtins step and associated
scripts.

Change-Id: Iaca5ffdaca4b5506e9401b17a7806d37fd7b1844
Reviewed-on: http://gerrit.cloudera.org:8080/11944
Reviewed-by: Tim Armstrong <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Don't load Hive builtin jars for dataload
> -----------------------------------------
>
>                 Key: IMPALA-7871
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7871
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Infrastructure
>    Affects Versions: Impala 3.1.0
>            Reporter: Joe McDonnell
>            Assignee: Joe McDonnell
>            Priority: Major
>
> One step in dataload is "Loading Hive Builtins", which copies a large number 
> of jars into HDFS (or whatever storage). This step takes a couple minutes on 
> HDFS dataload and 8 minutes on S3. Despite its name, I can't find any 
> indication that Hive or anything else uses these jars. Dataload and core 
> tests run fine without it. S3 can load data without it. There's no indication 
> that this is needed.
> Unless we find something using these jars, we should remove this step.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to