[
https://issues.apache.org/jira/browse/HIVE-8816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252225#comment-14252225
]
Brock Noland commented on HIVE-8816:
------------------------------------
Thank you! I think we want to do:
{noformat}
EXPLAIN EXTENDED SELECT * FROM
encryptedWith256BitsKeyDB.encryptedTableIn256BitsKey t1
JOIN encryptedWith128BitsKeyDB.encryptedTableIn128BitsKey t2 WHERE t1.key =
t2.key;
{noformat}
then in the same q-file:
actually execute the join:
{noformat}
SELECT * FROM encryptedWith256BitsKeyDB.encryptedTableIn256BitsKey t1
JOIN encryptedWith128BitsKeyDB.encryptedTableIn128BitsKey t2 WHERE t1.key =
t2.key;
{noformat}
Also please add {{--SORT_QUERY_RESULTS}} since different JVM's or execution
engines could order results differently.
> Create unit test join of two encrypted tables with different keys
> -----------------------------------------------------------------
>
> Key: HIVE-8816
> URL: https://issues.apache.org/jira/browse/HIVE-8816
> Project: Hive
> Issue Type: Sub-task
> Reporter: Brock Noland
> Assignee: Ferdinand Xu
> Fix For: encryption-branch
>
> Attachments: HIVE-8816.1.patch, HIVE-8816.patch
>
>
> NO PRECOMMIT TESTS
> The results should be inserted into a third table encrypted with a separate
> key.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
