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

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

                Author: ASF GitHub Bot
            Created on: 08/Aug/19 08:30
            Start Date: 08/Aug/19 08:30
    Worklog Time Spent: 10m 
      Work Description: hadoop-yetus commented on issue #1233: HDDS-1915. 
Remove hadoop script from ozone distribution
URL: https://github.com/apache/hadoop/pull/1233#issuecomment-519422885
 
 
   :confetti_ball: **+1 overall**
   
   
   
   
   
   
   | Vote | Subsystem | Runtime | Comment |
   |:----:|----------:|--------:|:--------|
   | 0 | reexec | 41 | Docker mode activated. |
   ||| _ Prechecks _ |
   | +1 | dupname | 0 | No case conflicting files found. |
   | 0 | shelldocs | 0 | Shelldocs was not available. |
   | +1 | @author | 0 | The patch does not contain any @author tags. |
   ||| _ trunk Compile Tests _ |
   | +1 | shadedclient | 730 | branch has no errors when building and testing 
our client artifacts. |
   ||| _ Patch Compile Tests _ |
   | +1 | shellcheck | 0 | There were no new shellcheck issues. |
   | +1 | whitespace | 0 | The patch has no whitespace issues. |
   | +1 | shadedclient | 636 | patch has no errors when building and testing 
our client artifacts. |
   ||| _ Other Tests _ |
   | +1 | asflicense | 28 | The patch does not generate ASF License warnings. |
   | | | 1541 | |
   
   
   | Subsystem | Report/Notes |
   |----------:|:-------------|
   | Docker | Client=19.03.1 Server=19.03.1 base: 
https://builds.apache.org/job/hadoop-multibranch/job/PR-1233/3/artifact/out/Dockerfile
 |
   | GITHUB PR | https://github.com/apache/hadoop/pull/1233 |
   | Optional Tests | dupname asflicense shellcheck shelldocs |
   | uname | Linux ea291fcd5650 4.4.0-157-generic #185-Ubuntu SMP Tue Jul 23 
09:17:01 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux |
   | Build tool | maven |
   | Personality | personality/hadoop.sh |
   | git revision | trunk / 00b5a27 |
   | Max. process+thread count | 422 (vs. ulimit of 5500) |
   | modules | C: hadoop-ozone/dist U: hadoop-ozone/dist |
   | Console output | 
https://builds.apache.org/job/hadoop-multibranch/job/PR-1233/3/console |
   | versions | git=2.7.4 maven=3.3.9 shellcheck=0.4.6 |
   | Powered by | Apache Yetus 0.10.0 http://yetus.apache.org |
   
   
   This message was automatically generated.
   
   
 
----------------------------------------------------------------
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: 291067)
    Time Spent: 50m  (was: 40m)

> Remove hadoop script from ozone distribution
> --------------------------------------------
>
>                 Key: HDDS-1915
>                 URL: https://issues.apache.org/jira/browse/HDDS-1915
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> /bin/hadoop script is included in the ozone distribution even if we a 
> dedicated /bin/ozone
> [~arp] reported that it can be confusing, for example "hadoop classpath" 
> returns with a bad classpath (ozone classpath <projectname>) should be used 
> instead.
> To avoid such confusions I suggest to remove the hadoop script from 
> distribution as ozone script already provides all the functionalities.
> It also helps as to reduce the dependencies between hadoop 3.2-SNAPSHOT and 
> ozone as we use the snapshot hadoop script as of now.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

Reply via email to