You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Stephen O'Donnell (Jira)" <ji...@apache.org> on 2023/08/09 09:19:00 UTC
[jira] [Resolved] (HDDS-1860) importContainer hard-codes KeyValue Container classes
[ https://issues.apache.org/jira/browse/HDDS-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen O'Donnell resolved HDDS-1860.
-------------------------------------
Resolution: Won't Fix
Resolving as we have re visioned the container layout since this was created, so this is likely no longer relevant.
> importContainer hard-codes KeyValue Container classes
> -----------------------------------------------------
>
> Key: HDDS-1860
> URL: https://issues.apache.org/jira/browse/HDDS-1860
> Project: Apache Ozone
> 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.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org