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

ASF GitHub Bot logged work on HADOOP-17720:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 24/May/21 09:05
            Start Date: 24/May/21 09:05
    Worklog Time Spent: 10m 
      Work Description: tasanuma commented on pull request #3031:
URL: https://github.com/apache/hadoop/pull/3031#issuecomment-846898948


   @virajjasani It would be a lot of work, but I think import sentences should 
be written in alphabetical order as much as possible. I mean  `import 
org.apache.hadoop.util.Sets;` should be written in the same place where the 
other `org.apache.hadoop.util` classes are imported. (IntelliJ will add the 
import statement in the appropriate place if your press Alt+Enter while the 
class is still unimported.)


-- 
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: 601074)
    Time Spent: 1h 10m  (was: 1h)

> Replace Guava Sets usage by Hadoop's own Sets in hadoop-hdfs-project
> --------------------------------------------------------------------
>
>                 Key: HADOOP-17720
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17720
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>




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