hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8433) blockToken is not set in constructInternalBlock and parseStripedBlockGroup in StripedBlockUtil
Date Tue, 14 Jul 2015 20:37:04 GMT

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

Jing Zhao commented on HDFS-8433:
---------------------------------

bq. This time, we don't need BlockIdRange class. We extends the fields of BlockTokenIdentifier.
(See BlockTokenIdentifier#readFields(..) / write(..) )

Maybe more details? Not sure if I catch the idea here. How to avoid changing the readFields/writeFields
but still adding a new field?

> blockToken is not set in constructInternalBlock and parseStripedBlockGroup in StripedBlockUtil
> ----------------------------------------------------------------------------------------------
>
>                 Key: HDFS-8433
>                 URL: https://issues.apache.org/jira/browse/HDFS-8433
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Walter Su
>         Attachments: HDFS-8433-HDFS-7285.02.patch, HDFS-8433.00.patch, HDFS-8433.01.patch
>
>
> The blockToken provided in LocatedStripedBlock is not used to create LocatedBlock in
constructInternalBlock and parseStripedBlockGroup in StripedBlockUtil.
> We should also add ec tests with security on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message