[
https://issues.apache.org/jira/browse/HIVE-18341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
anishek updated HIVE-18341:
---------------------------
Attachment: HIVE-18341.0.patch
[~thejas] Can you please help understand the failing scenario for this.
I have created a test where there are two different encrypting zones with
different keys for different databases in the same cluster and doing
replication between them should have failed, but it all seems to work. Is this
just an optimization for distcp to copy over the raw bytes ? How do i
differentiate between the distcp using the /.reserved/raw vs regular copy
between different two different encryption zones.
> Add repl load support for adding "raw" namespace for TDE with same encryption
> keys
> ----------------------------------------------------------------------------------
>
> Key: HIVE-18341
> URL: https://issues.apache.org/jira/browse/HIVE-18341
> Project: Hive
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: anishek
> Assignee: anishek
> Fix For: 3.0.0
>
> Attachments: HIVE-18341.0.patch
>
>
> https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/TransparentEncryption.html#Running_as_the_superuser
> "a new virtual path prefix, /.reserved/raw/, that gives superusers direct
> access to the underlying block data in the filesystem. This allows superusers
> to distcp data without needing having access to encryption keys, and also
> avoids the overhead of decrypting and re-encrypting data."
> We need to introduce a new option in "Repl Load" command that will change the
> files being copied in distcp to have this "/.reserved/raw/" namespace before
> the file paths.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
