[ 
https://issues.apache.org/jira/browse/MAPREDUCE-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951141#comment-16951141
 ] 

Hadoop QA commented on MAPREDUCE-7141:
--------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  9s{color} 
| {color:red} MAPREDUCE-7141 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | MAPREDUCE-7141 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12954487/MAPREDUCE-7141-001.patch
 |
| Console output | 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/7673/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was automatically generated.



> Allow KMS generated spill encryption keys
> -----------------------------------------
>
>                 Key: MAPREDUCE-7141
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7141
>             Project: Hadoop Map/Reduce
>          Issue Type: Task
>            Reporter: Kuhu Shukla
>            Assignee: Kuhu Shukla
>            Priority: Major
>         Attachments: MAPREDUCE-7141-001.patch
>
>
> Currently the only way an encryption key for task spills is generated is by 
> the AM's key generator. This JIRA tracks the work required to add KMS support 
> to this key's generation allowing fault tolerance to AM failures/re-runs and 
> also give another option to the client on how it wants the keys to be created.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to