ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3877) Clarify if IgfsFile -> FileStatus conversion should treat groupBlockSize as blockSize
Date Thu, 29 Dec 2016 07:47:58 GMT

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

Vladimir Ozerov commented on IGNITE-3877:
-----------------------------------------

Closing as the whole fix is inside IGNITE-481.

> Clarify if IgfsFile -> FileStatus conversion should treat groupBlockSize as blockSize
> -------------------------------------------------------------------------------------
>
>                 Key: IGNITE-3877
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3877
>             Project: Ignite
>          Issue Type: Bug
>          Components: IGFS
>    Affects Versions: 1.6
>            Reporter: Ivan Veselovsky
>            Assignee: Vladimir Ozerov
>             Fix For: 2.0
>
>
> During Metrics tests repairing test org.apache.ignite.igfs.Hadoop1DualAbstractTest#testMetricsBlock
revealed the following problem:
> org.apache.ignite.hadoop.fs.v1.IgniteHadoopFileSystem#convert(org.apache.ignite.igfs.IgfsFile)
method treats groupBlockSize as blockSize for Hadoop FileStatus. groupBlockSize can be several
times larger than blockSize, so blockSize in status gets different to that in original IgfsFile
.
> changing file.groupBlockSize() to file.blockSize()  fixes problem in metrics tests, but
creates problems in Hadoop tests that are bound to splits calculation, since split calculation
related to blockSizes.
> Need to 
> 1) clarify if the treatment of groupBlcokSize was intentional.
> 2) fix either metrics tests or Hadoop tests. 



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

Mime
View raw message