[
https://issues.apache.org/jira/browse/SQOOP-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597722#comment-13597722
]
Jarek Jarcec Cecho commented on SQOOP-917:
------------------------------------------
This is indeed interesting idea. Sqoop 1 is more focusing to be highly
efficient data transfer tool. The way one can think about it is that it's doing
only E (extract) and L (load) from usual ETL (extract-transform-load)
perspective. Thus no transform like data encryption. We were thinking about
introducing the T (transform) into Sqoop 2, but that is still open question.
> Encrypt data in Hive via Sqoop.
> -------------------------------
>
> Key: SQOOP-917
> URL: https://issues.apache.org/jira/browse/SQOOP-917
> Project: Sqoop
> Issue Type: Wish
> Components: connectors/oracle
> Affects Versions: 1.4.0-incubating
> Reporter: Santosh
> Labels: sqoop
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi, I am trying to import Oracle data into Hive via Sqoop. I have some secret
> data in oracle which i would like to have in Hive as encrypted(Security) (Do
> not want to disclose secret data in Hive/HDFS/HBase). Is it possible to do
> that?
> Note: Only few Oracle columns data(Secret Columns) needs to be encrypted in
> Hive while transferring via Sqoop.
> Use Case is to Transfer the data further from Hive to Amazon DynamoDB.
> Flow: Oralce DB -->> Hive -->> DynamoDB
> Thanks San.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
