[
https://issues.apache.org/jira/browse/HADOOP-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-2657:
-------------------------------------
Attachment: flush8.patch
Findbugs reported that packetSize was not synchronized correctly in
setPacketSize() method. However, this method is called only by the unit tests
and that too at the beginning of the test. So, there isn't a real problem.
However, to get rid of the findbugs warning, I syncronized this method too.
This still does not fix another findbugs warning that this patch generates
because it complains about accessing "streamer". This warning is harmless and
can be safely ignored.
> Enhancements to DFSClient to support flushing data at any point in time
> -----------------------------------------------------------------------
>
> Key: HADOOP-2657
> URL: https://issues.apache.org/jira/browse/HADOOP-2657
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Fix For: 0.17.0
>
> Attachments: flush.patch, flush2.patch, flush3.patch, flush4.patch,
> flush5.patch, flush6.patch, flush7.patch, flush8.patch
>
>
> The HDFS Append Design (HADOOP-1700) requires that there be a public API to
> flush data written to a HDFS file that can be invoked by an application. This
> API (popularly referred to a fflush(OutputStream)) will ensure that data
> written to the DFSOutputStream is flushed to datanodes and any required
> metadata is persisted on Namenode.
> This API has to handle the case when the client decides to flush after
> writing data that is not a exact multiple of io.bytes.per.checksum.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
