[
https://issues.apache.org/jira/browse/HIVE-9167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253514#comment-14253514
]
Sergio Peña commented on HIVE-9167:
-----------------------------------
Hi [~Ferd], What I am trying to do with the crypto commands is that we can
create encryption zones for specific tables during our tests.
Users will have tables with different encryption zones, and I'd like to test
different queries that work with these tables. The encryption support in Hive
does a Copy of data when a query uses two tables with different encryption
zones, and a Move when they're in the same encryption zone (an encrypted DB is
just an encryption zone, so all queries will use Move).
Also, I think this looks more readable when another developer reads the .q
files.
> Enhance encryption testing framework to allow create keys & zones inside .q
> files
> ---------------------------------------------------------------------------------
>
> Key: HIVE-9167
> URL: https://issues.apache.org/jira/browse/HIVE-9167
> Project: Hive
> Issue Type: Sub-task
> Reporter: Sergio Peña
> Assignee: Sergio Peña
>
> The current implementation of the encryption testing framework on HIVE-8900
> initializes a couple of encrypted databases to be used on .q test files. This
> is useful in order to make tests small, but it does not test all details
> found on the encryption implementation, such as: encrypted tables with
> different encryption strength in the same database.
> We need to allow this kind of encryption as it is how it will be used in the
> real world where a database will have a few encrypted tables (not all the DB).
> Also, we need to make this encryption framework flexible so that we can
> create/delete keys & zones on demand when running the .q files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
