[
https://issues.apache.org/jira/browse/HIVE-9167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252587#comment-14252587
]
Sergio Peña commented on HIVE-9167:
-----------------------------------
[~Ferd] [~brocknoland], I was thinking about how we could improve the .q test
files for encryption testing, and I think .q tests should be something like
this:
{noformat}
DROP TABLE IF EXISTS encrypted_table;
CREATE TABLE encrypted_table (key STRING, value STRING) LOCATION
'/user/hive/warehouse/encrypted_table';
crypto_helper create_key key1;
crypto_helper create_zone key1 /user/hive/warehouse/encrypted_table;
-- Test loading data from the local filesystem;
LOAD DATA LOCAL INPATH '../../data/files/kv1.txt' OVERWRITE INTO TABLE
encrypted_table;
SELECT * FROM encrypted_table;
-- Test loading data from the hdfs filesystem;
dfs -copyFromLocal ../../data/files/kv1.txt hdfs:///tmp/kv1.txt;
LOAD DATA INPATH '/tmp/kv1.txt' OVERWRITE INTO TABLE encrypted_table;
SELECT * FROM encrypted_table;
DROP TABLE encrypted_table;
crypto_helper delete_key key1;
{noformat}
The 'crypto_helper' is a command where we can use it into the .q files in order
to create keys & zones on demand. This will also help us run some complex
INSERT queries with different encryption strength.
The above statements are just an example about how we can improve this testing
framework.
What do you think?
I am going to upload a patch for a partial review.
> 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)
