[
https://issues.apache.org/jira/browse/HDDS-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559991#comment-16559991
]
Tsz Wo Nicholas Sze commented on HDDS-226:
------------------------------------------
Currently, BlockID, by its name, contains just IDs. It is immutable and it can
be used as key in hash table. If length is a part of a BlockID, it may lose
these nice properties. Question: would a.equals(b) == true if a and b have the
same id values but different length?
If there is a need to add length, BlockID should be renamed to something like
BlockInfo (or just add a BlockInfo subclass). Otherwise, it becomes very
confusing.
> Client should update block length in OM while committing the key
> ----------------------------------------------------------------
>
> Key: HDDS-226
> URL: https://issues.apache.org/jira/browse/HDDS-226
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Manager
> Reporter: Mukul Kumar Singh
> Assignee: Shashikant Banerjee
> Priority: Major
> Fix For: 0.2.1
>
> Attachments: HDDS-226.00.patch, HDDS-226.01.patch, HDDS-226.02.patch,
> HDDS-226.03.patch, HDDS-226.04.patch, HDDS-226.05.patch
>
>
> Currently the client allocate a key of size with SCM block size, however a
> client can always write smaller amount of data and close the key. The block
> length in this case should be updated on OM.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
