[jira] [Updated] (HDDS-1860) importContainer hard-codes KeyValue Container classes

["Prashant Pogde (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDDS-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prashant Pogde updated HDDS-1860:
---------------------------------
    Target Version/s: 1.2.0

I am managing the 1.1.0 release and we currently have more than 600 issues targeted for 1.1.0. I am moving the target field to 1.2.0. 

If you are actively working on this jira and believe this should be targeted to 1.1.0 release, Please change the target field back to 1.1.0 before Feb 05, 2021. 

> importContainer hard-codes KeyValue Container classes
> -----------------------------------------------------
>
>                 Key: HDDS-1860
>                 URL: https://issues.apache.org/jira/browse/HDDS-1860
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Arpit Agarwal
>            Priority: Major
>
> importContainer should use the same instantiation logic as the DataNode startup code. It should not hard-code the KeyValueContainer classes:
> {code}
>     KeyValueContainerData containerData =
>         new KeyValueContainerData(containerID,
>             maxSize, originPipelineId, originNodeId);
>     KeyValueContainer container = new KeyValueContainer(containerData,
>         conf);
> {code}
> This will break when we revision the container layout. Also sharing the instantiation logic will save code.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org