yzhang559 opened a new pull request, #6860:
URL: https://github.com/apache/hadoop/pull/6860

   … queues for keys.
   
   <!--
     Thanks for sending a pull request!
       1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
       2. Make sure your PR title starts with JIRA issue id, e.g., 
'HADOOP-17799. Your PR title ...'.
   -->
   JIRA = [HDFS-13603](https://issues.apache.org/jira/browse/HDFS-13603)
   ### Description of PR
   throw IOException at last if cache warmup fail for any keys, continue to 
warmup other keys.
   
   This is the changes in hadoop-common from PR 
https://github.com/apache/hadoop/pull/6774
   
   
   ### How was this patch tested?
   new unit test is added
   ```
   mvn test -Dtest=TestValueQueue
   [INFO] Running org.apache.hadoop.crypto.key.TestValueQueue
   [INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
13.077 s - in org.apache.hadoop.crypto.key.TestValueQueue
   ```
   
   ### For code changes:
   
   - [x] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to