See https://builds.apache.org/job/Hadoop-Common-trunk/1526/changes
See https://builds.apache.org/job/Hadoop-common-trunk-Java8/228/changes
Apologize if I wasn't clear
Is the EZ key version same as an alias for the key?
yup
the EDEK along with the EZ key version is stored in the FIleInfo
FileInfo contains both EDEK and EZ key version. The FileInfo (you can look
at the *org.apache.hadoop.fs.FileEncryptionInfo* class for more info)
Hello Sitaraman,
It is the EZ key version that is used to generate the EDEK (and which is
ultimately stored in the encrypted file's extended attributes
'*raw.hdfs.crypto.encryption.info
http://raw.hdfs.crypto.encryption.info*'), not really the the EZ key
itself (which is stored in the directory's
Hi,
We touched this topic before but it was put on hold. I'd like to bring it
to our attention again.
From time to time we saw changes that work fine in trunk but not branch-2,
and we don't catch the issue in a timely manner. The difference between
trunk and branch-2 is sufficient to justify
pre-commit will already test on branch-2 provided you follow the patch
naming guidelines.
there is also a branch-2 specific jenkins job:
https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-branch2/
I'd suggest starting by looking at that job and filing jiras to address
whatever the
