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

Hudson commented on HDDS-123:
-----------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14547 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/14547/])
HDDS-123:ContainerSet class to manage ContainerMap. Contributed by (bharat: rev 
977c8cd1665b42ba45e9d21655262ef78714b716)
* (add) 
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/impl/ContainerSet.java
* (add) 
hadoop-hdds/container-service/src/test/java/org/apache/hadoop/ozone/container/common/impl/TestContainerSet.java
* (edit) 
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/impl/KeyValueContainer.java
* (edit) 
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/impl/ContainerData.java


> ContainerSet class to manage ContainerMap 
> ------------------------------------------
>
>                 Key: HDDS-123
>                 URL: https://issues.apache.org/jira/browse/HDDS-123
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>             Fix For: 0.2.1
>
>         Attachments: HDDS-123-HDDS-48.00.patch, HDDS-123-HDDS-48.01.patch, 
> HDDS-123-HDDS-48.02.patch, HDDS-123-HDDS-48.03.patch, 
> HDDS-123-HDDS-48.04.patch, HDDS-123-HDDS-48.05.patch
>
>
> Create a ContainerSet class, which manages containerMap.
> Previously container map is in ContainerManagerImpl, with refactoring work it 
> should be moved to ContainerSet. 
> This class should handle add/get/remove container from containerMap.
> And also now it should handle containerReport.



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