You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Bharat Viswanadham (JIRA)" <ji...@apache.org> on 2018/07/03 00:29:00 UTC
[jira] [Comment Edited] (HDDS-176) Add keyCount and container
maximum size to ContainerData
[ https://issues.apache.org/jira/browse/HDDS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16530616#comment-16530616 ]
Bharat Viswanadham edited comment on HDDS-176 at 7/3/18 12:28 AM:
------------------------------------------------------------------
Hi [~hanishakoneru]
Thanks for the review.
Addressed review comments in patch v01.
Moved the maxSize logic to KeyValueHandler.
was (Author: bharatviswa):
Hi [~hanishakoneru]
Thanks for the review.
Addressed review comments in patch v01.
> Add keyCount and container maximum size to ContainerData
> --------------------------------------------------------
>
> Key: HDDS-176
> URL: https://issues.apache.org/jira/browse/HDDS-176
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
> Fix For: 0.2.1
>
> Attachments: HDDS-176-HDDS-48.00.patch, HDDS-176-HDDS-48.01.patch
>
>
> # ContainerData, should hold container maximum size, and this should be serialized into .container file. This is needed because after some time, container size can be changed. So, old containers will have different max size than the newly created containers.
> # And also add KeyCount which says the number of keys in the container.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org