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

Da Zhou commented on HADOOP-15544:
----------------------------------

Thank you [[email protected]] for sharing the steps.  At my end I can run the 
hadoop cmd without issue.

What I did: I followed the steps you shared, then append *$HADOOP_CLASSPATH* 
with the required jars path (azure jar path and 
/hadoop-dist/target/hadoop-3.2.0-SNAPSHOT/share/hadoop/tools/lib/*).

After that I tried WASB:
{code:java}
./bin/hadoop fs -ls 
wasb://TEST_CONTAINER_NAME@TEST_ACCOUNT.blob.core.windows.net/{code}
Then tried ABFS:
{code:java}
./bin/hadoop fs -ls 
abfs://TEST_CONTAINER_NAME@TEST_ACCOUNT.dfs.core.windows.net/{code}
Both can return the results successfully.

Could you share your setting for core-site.xml  and the failure message  with 
me? I guess it might be related to the configuration.

Thanks,
Da

> ABFS: validate packing, transient classpath, hadoop fs CLI
> ----------------------------------------------------------
>
>                 Key: HADOOP-15544
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15544
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure
>    Affects Versions: 3.2
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>         Attachments: dependencies.txt
>
>
> Validate the packaging and dependencies of ABFS
> * hadoop-cloud-storage artifact to export everything needed
> * {{hadoop fs -ls abfs://path}} to work in ASF distributions
> * check transient CP (e.g spark)
> Spark master;s hadoop-cloud module depends on hadoop-cloud-storage if you 
> build with the hadoop-3.1 profile, so it should automatically get in there. 
> Just need to check that it picks it up too



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