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

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

                Author: ASF GitHub Bot
            Created on: 27/Aug/19 17:01
            Start Date: 27/Aug/19 17:01
    Worklog Time Spent: 10m 
      Work Description: elek commented on issue #1351: HDDS-2037. Fix hadoop 
version in pom.ozone.xml.
URL: https://github.com/apache/hadoop/pull/1351#issuecomment-525392522
 
 
   I think we already started to use 3.2 specific APIs. Some of our 
requirements are included in hadoop 3.2 but not in 3.1.
   
   If we need any fixes in the hadoop common we should wait until hadoop 3.3. 
Using 3.1 it would be even harder. 
   
   I would use 3.2 as before.
 
----------------------------------------------------------------
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: 302219)
    Time Spent: 1.5h  (was: 1h 20m)

> Fix hadoop version in pom.ozone.xml
> -----------------------------------
>
>                 Key: HDDS-2037
>                 URL: https://issues.apache.org/jira/browse/HDDS-2037
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Nanda kumar
>            Assignee: Nanda kumar
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> The hadoop version in pom.ozone.xml is pointing to SNAPSHOT version, this has 
> to be fixed.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

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

Reply via email to