[
https://issues.apache.org/jira/browse/HADOOP-10603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998428#comment-13998428
]
Yi Liu commented on HADOOP-10603:
---------------------------------
In HADOOP-10047, @Gopal V add a directbuffer Decompressor API to hadoop:
{quote}
With the Zero-Copy reads in HDFS (HDFS-5260), it becomes important to perform
all I/O operations without copying data into byte[] buffers or other buffers
which wrap over them.
This is a proposal for adding a DirectDecompressor interface to the
io.compress, to indicate codecs which want to surface the direct buffer layer
upwards.
The implementation should work with direct heap/mmap buffers and cannot assume
.array() availability.
{quote}
So we can have similar API for encryption/decryption.
In HADOOP-10591, direct buffer allocating/deallocating is discussed. We should
have same consideration.
BTW, crypto streams test in HDFS is addressed in HDFS-6405. We will also have
common test for this JIRA.
> Crypto input and output streams implementing Hadoop stream interfaces
> ---------------------------------------------------------------------
>
> Key: HADOOP-10603
> URL: https://issues.apache.org/jira/browse/HADOOP-10603
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: security
> Reporter: Alejandro Abdelnur
> Assignee: Yi Liu
> Fix For: 3.0.0
>
> Attachments: HADOOP-10603.patch
>
>
> A common set of Crypto Input/Output streams. They would be used by
> CryptoFileSystem, HDFS encryption, MapReduce intermediate data and spills.
> Note we cannot use the JDK Cipher Input/Output streams directly because we
> need to support the additional interfaces that the Hadoop FileSystem streams
> implement (Seekable, PositionedReadable, ByteBufferReadable,
> HasFileDescriptor, CanSetDropBehind, CanSetReadahead,
> HasEnhancedByteBufferAccess, Syncable, CanSetDropBehind).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
