[ 
https://issues.apache.org/jira/browse/HDDS-2121?focusedWorklogId=314623&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-314623
 ]

ASF GitHub Bot logged work on HDDS-2121:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Sep/19 20:25
            Start Date: 18/Sep/19 20:25
    Worklog Time Spent: 10m 
      Work Description: bharatviswa504 commented on issue #1452: HDDS-2121. 
Create a shaded ozone filesystem (client) jar
URL: https://github.com/apache/hadoop/pull/1452#issuecomment-532851470
 
 
   `$ ./test.sh 
   Removing network hadoop32_default
   WARNING: Network hadoop32_default not found.
   Creating network "hadoop32_default" with the default driver
   Creating hadoop32_scm_1      ... done
   Creating hadoop32_datanode_1 ... done
   Creating hadoop32_datanode_2 ... done
   Creating hadoop32_datanode_3 ... done
   Creating hadoop32_nm_1       ... done
   Creating hadoop32_rm_1       ... done
   Creating hadoop32_s3g_1      ... done
   Creating hadoop32_om_1       ... done
   3 datanodes are up and registered to the scm
   
==============================================================================
   hadoop32-createmrenv :: Create directories required for MR test              
 
   
==============================================================================
   Create test volume, bucket and key                                    | PASS 
|
   
------------------------------------------------------------------------------
   Create user dir for hadoop                                            | PASS 
|
   
------------------------------------------------------------------------------
   hadoop32-createmrenv :: Create directories required for MR test       | PASS 
|
   2 critical tests, 2 passed, 0 failed
   2 tests total, 2 passed, 0 failed
   
==============================================================================
   Output:  
/tmp/smoketest/hadoop32/result/robot-hadoop32-hadoop32-createmrenv-scm.xml
   
==============================================================================
   hadoop32-hadoopo3fs :: Test ozone fs with hadoopfs                           
 
   
==============================================================================
   Test hadoop dfs                                                       | PASS 
|
   
------------------------------------------------------------------------------
   hadoop32-hadoopo3fs :: Test ozone fs with hadoopfs                    | PASS 
|
   1 critical test, 1 passed, 0 failed
   1 test total, 1 passed, 0 failed
   
==============================================================================
   Output:  
/tmp/smoketest/hadoop32/result/robot-hadoop32-hadoop32-hadoopo3fs-rm.xml
   
==============================================================================
   hadoop32-mapreduce :: Execute MR jobs                                        
 
   
==============================================================================
   Execute PI calculation                                                | PASS 
|
   
------------------------------------------------------------------------------
   Execute WordCount                                                     | PASS 
|
   
------------------------------------------------------------------------------
   hadoop32-mapreduce :: Execute MR jobs                                 | PASS 
|
   2 critical tests, 2 passed, 0 failed
   2 tests total, 2 passed, 0 failed
   
==============================================================================
   Output:  
/tmp/smoketest/hadoop32/result/robot-hadoop32-hadoop32-mapreduce-rm.xml
   Stopping hadoop32_s3g_1      ... done
   Stopping hadoop32_datanode_1 ... done
   Stopping hadoop32_nm_1       ... done
   Stopping hadoop32_datanode_3 ... done
   Stopping hadoop32_datanode_2 ... done
   Stopping hadoop32_om_1       ... done
   Stopping hadoop32_scm_1      ... done
   Stopping hadoop32_rm_1       ... done
   Removing hadoop32_s3g_1      ... done
   Removing hadoop32_datanode_1 ... done
   Removing hadoop32_nm_1       ... done
   Removing hadoop32_datanode_3 ... done
   Removing hadoop32_datanode_2 ... done
   Removing hadoop32_om_1       ... done
   Removing hadoop32_scm_1      ... done
   Removing hadoop32_rm_1       ... done
   Removing network hadoop32_default
   Log:     
/Users/bviswanadham/workspace/myozone/hadoop/hadoop-ozone/dist/target/ozone-0.5.0-SNAPSHOT/compose/ozone-mr/hadoop32/result/log.html
   Report:  
/Users/bviswanadham/workspace/myozone/hadoop/hadoop-ozone/dist/target/ozone-0.5.0-SNAPSHOT/compose/ozone-mr/hadoop32/result/report.html`
   
   Ran it locally test passed, the test failure is not related to this patch. 
   
   I will commit this to the trunk. Thank You @elek for the improvement.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 314623)
    Time Spent: 2h  (was: 1h 50m)

> Create a shaded ozone filesystem (client) jar
> ---------------------------------------------
>
>                 Key: HDDS-2121
>                 URL: https://issues.apache.org/jira/browse/HDDS-2121
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: build
>            Reporter: Arpit Agarwal
>            Assignee: Elek, Marton
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 0.5.0
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> We need a shaded Ozonefs jar that does not include Hadoop ecosystem 
> components (Hadoop, HDFS, Ratis, Zookeeper).
> A common expected use case for Ozone is Hadoop clients (3.2.0 and later) 
> wanting to access Ozone via the Ozone Filesystem interface. For these 
> clients, we want to add Ozone file system jar to the classpath, however we 
> want to use Hadoop ecosystem dependencies that are `provided` and already 
> expected to be in the client classpath.
> Note that this is different from the legacy jar which bundles a shaded Hadoop 
> 3.2.0.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to