hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6377) Unify xattr name and value limits into a single limit
Date Mon, 12 May 2014 22:38:17 GMT

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

Andrew Wang commented on HDFS-6377:

Existing filesystems go both ways on this. Splitting makes sense if you want to stash the
names in the inode and then store the values in blocks, but we don't do that.

I'll also add that the name is a String while the value is a byte[]. {{String#length}} returns
the # of unicode code units, not the # of bytes. It might make sense to do some kind of conversion
here to get a more accurate accounting of space usage.

One other cleanup that'd be good to do is using Hash and EqualsBuilder in XAttr to shorten
those functions.

> Unify xattr name and value limits into a single limit
> -----------------------------------------------------
>                 Key: HDFS-6377
>                 URL: https://issues.apache.org/jira/browse/HDFS-6377
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>    Affects Versions: HDFS XAttrs (HDFS-2006)
>            Reporter: Andrew Wang
> Instead of having separate limits and config options for the size of an xattr's name
and value, let's use a single limit.

This message was sent by Atlassian JIRA

View raw message