You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Christopher Tubbs (Jira)" <ji...@apache.org> on 2020/03/11 21:40:00 UTC

[jira] [Resolved] (ACCUMULO-2669) NoFlushOutputStream always in use in DfsLogger

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

Christopher Tubbs resolved ACCUMULO-2669.
-----------------------------------------
    Resolution: Invalid

Crypto was reworked for 2.x. This is now OBE. If this is still an issue, please open a new issue or pull request at https://github.com/apache/accumulo/issues

> 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
>
> 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
(v8.3.4#803005)