hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Chen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5025) Key Distribution and Management for supporting crypto codec in Map Reduce
Date Mon, 25 Feb 2013 09:00:20 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jerry Chen updated MAPREDUCE-5025:

    Attachment: MAPREDUCE-5025.patch
> Key Distribution and Management for supporting crypto codec in Map Reduce
> -------------------------------------------------------------------------
>                 Key: MAPREDUCE-5025
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5025
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: security
>    Affects Versions: trunk
>            Reporter: Jerry Chen
>            Assignee: Jerry Chen
>         Attachments: MAPREDUCE-5025.patch
>   Original Estimate: 504h
>  Remaining Estimate: 504h
> This task defines the work to enable Map Reduce to utilize the Crypto Codec framework
to support encryption and decryption of data during MapReduce Job.
> According to the some real use case and discussions from the community, for encryption
and decryption files in Map Reduce, we have the following requirements:
>   1. Different stages (input, output, intermediate output) should have the flexibility
to choose whether encrypt or not, as well as which crypto codec to use.
>   2. Different stages may have different scheme of providing the keys.
>   3. Different Files (for example, different input files) may have or use different keys.

>   4. Support a flexible way of retrieving keys for encryption or decryption.
> So this task defines and provides the framework for supporting these requirements as
well as the implementations for common use and key retrieving scenarios.
> The design document of this part is included in the Hadoop Crypto Design attached in

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

View raw message