[
https://issues.apache.org/jira/browse/HIVE-9167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252716#comment-14252716
]
Ferdinand Xu commented on HIVE-9167:
------------------------------------
Hi [~spena], do we real need add the crypto command for the beeline? We can use
the explain statement to show the output directory(in quotes) "EXPLAIN
AUTHORIZATION query" or add one more explain statement for the purpose. I think
explain authorization will be OK for this purpose. At this point, the output
for query test is empty and I am planing to file a jira for that. Any thoughts?
https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Explain
> 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)
