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

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

Commit 985d2d1c1b8f2ad801341eeed897e1c51bc16718 in impala's branch 
refs/heads/2.x from [~dknupp]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=985d2d1 ]

IMPALA-4464: Remove /bin/remote_data_load.py

This file was started before the ASF project was set up, and
committed as-is. However, it relies on some internal resources
not generally available to the external Apache community at large,
and so serves no purpose in that context.

Change-Id: I002efae6ad538d371680ce23099277708ed67e0e
Reviewed-on: http://gerrit.cloudera.org:8080/10388
Reviewed-by: Philip Zeyliger <[email protected]>
Tested-by: David Knupp <[email protected]>


> Remove remote_data_load.py
> --------------------------
>
>                 Key: IMPALA-4464
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4464
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Infrastructure
>    Affects Versions: Impala 2.8.0
>            Reporter: David Knupp
>            Assignee: David Knupp
>            Priority: Major
>              Labels: remote_cluster_test
>
> A patch was recently submitted that allows data load and end-end tests to run 
> against a remote cluster. At its core was this file:
> https://github.com/apache/incubator-impala/blob/master/bin/remote_data_load.py
> However, while this script relies on several changes to existing build and 
> test scripts, nothing else in turns relies on it. In retrospect, it does not 
> make sense to have this script in the Impala repo if nothing can use it 
> externally.



--
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