TezQA commented on TEZ-3916:

{color:red}-1 overall{color}.  Here are the results of testing the latest 
  against master revision 919d328.

    {color:green}+1 @author{color}.  The patch does not contain any @author 

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 3.0.1) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2857//console

This message is automatically generated.

> Add hadoop-azure-datalake jar to azure profile
> ----------------------------------------------
>                 Key: TEZ-3916
>                 URL: https://issues.apache.org/jira/browse/TEZ-3916
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Eric Wohlstadter
>            Assignee: Eric Wohlstadter
>            Priority: Critical
>             Fix For: 0.10.0
>         Attachments: TEZ-3916.1.patch, TEZ-3916.2.patch, TEZ-3916.3.patch
> This jar is required for secure access to Azure object storage: 
> https://hadoop.apache.org/docs/current/hadoop-azure-datalake/index.html
> There is already an azure profile in Tez but it doesn't include this jar.
> Since the jar is only supported on Hadoop 2.8+, will either need to:
> 1. Determine that including it in a 2.7 build is fine
> 2. Or if it is not fine, then include the jar only when both the 2.8 profile 
> and the azure profile are activated

This message was sent by Atlassian JIRA

Reply via email to