[
https://issues.apache.org/jira/browse/HIVE-23553?focusedWorklogId=545313&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-545313
]
ASF GitHub Bot logged work on HIVE-23553:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 01/Feb/21 13:05
Start Date: 01/Feb/21 13:05
Worklog Time Spent: 10m
Work Description: pgaref edited a comment on pull request #1823:
URL: https://github.com/apache/hive/pull/1823#issuecomment-769755146
> I only partially reviewed this. Will continue reviewing.
> One question: I see we do not care about column encryption related
arguments in multiple places. Is it because column encryption is not supported?
Hey @mustafaiman good question with a complicated answer -- while creating
this I also did some digging to find out whats supported and what not. To sum
up my findings:
- It looks like we are currently able to encrypt entire tables and/or data
on hdfs using kms: HIVE-8065
- Support for column level encryption/decryption (passing some encryption
setting to the Table props and let Hive take care of the rest) started more
than a while ago as part of HIVE-6329
- There was a community discussion as part of HIVE-21848 to unify
encryption table properties (at least for ORC and Parquet) that concluded in
the accepted options
- However, these properties are still not propagated to the tables:
HIVE-21849
I believe part of the reason is that Hive already integrates with Apache
Ranger that can restrict user access to particular columns and also adds
data-masking on top.
However, I am more than happy discussing the revival of column encryption at
some point.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 545313)
Time Spent: 6h (was: 5h 50m)
> Upgrade ORC version to 1.6.7
> ----------------------------
>
> Key: HIVE-23553
> URL: https://issues.apache.org/jira/browse/HIVE-23553
> Project: Hive
> Issue Type: Improvement
> Reporter: Panagiotis Garefalakis
> Assignee: Panagiotis Garefalakis
> Priority: Major
> Labels: pull-request-available
> Time Spent: 6h
> Remaining Estimate: 0h
>
> Apache Hive is currently on 1.5.X version and in order to take advantage of
> the latest ORC improvements such as column encryption we have to bump to
> 1.6.X.
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343288&styleName=&projectId=12318320&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED_4ae78f19321c7fb1e7f337fba1dd90af751d8810_lin
> Even though ORC reader could work out of the box, HIVE LLAP is heavily
> depending on internal ORC APIs e.g., to retrieve and store File Footers,
> Tails, streams – un/compress RG data etc. As there ware many internal changes
> from 1.5 to 1.6 (Input stream offsets, relative BufferChunks etc.) the
> upgrade is not straightforward.
> This Umbrella Jira tracks this upgrade effort.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
