hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-5804) neither s3.block.size not fs.s3.block.size are honoured
Date Wed, 03 Jun 2009 11:36:07 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tom White resolved HADOOP-5804.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.21.0
         Assignee: Tom White

Fixed as a part of HADOOP-5861.

> neither s3.block.size not fs.s3.block.size are honoured
> -------------------------------------------------------
>
>                 Key: HADOOP-5804
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5804
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 0.18.2, 0.19.1, 0.20.0
>         Environment: all
>            Reporter: Mathieu Poumeyrol
>            Assignee: Tom White
>             Fix For: 0.21.0
>
>
> S3FileSystem does not override FileSystem.getDefaultBlockSize(), so the s3 default block
size is actualy controlled by fs.local.block.size
> As far as I can see, the s3 block size specific parameters (either with or without the
fs. prefix) are read nowhere.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message