[
https://issues.apache.org/jira/browse/ACCUMULO-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973427#comment-13973427
]
John Vines commented on ACCUMULO-2669:
--------------------------------------
The exception is, if we can guarantee that flush() calls will never cause the
dfsoutput stream to react. And even then, I think I have a bit more comfort
knowing that we would not be affected by any behavior changes in that space,
but that's just me
> NoFlushOutputStream always in use in DfsLogger
> ----------------------------------------------
>
> Key: ACCUMULO-2669
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2669
> Project: Accumulo
> Issue Type: Bug
> Affects Versions: 1.6.0
> Reporter: Jonathan Park
> Priority: Minor
> Fix For: 1.6.1
>
>
> I may be misreading the implementation of DfsLogger, but it looks like we
> always make use of the NoFlushOutputStream, even if encryption isn't enabled.
> There appears to be a faulty check in the DfsLogger.open() implementation
> that I don't believe can be satisfied (line 384).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
