[
https://issues.apache.org/jira/browse/YETUS-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved YETUS-264.
------------------------------------
Resolution: Won't Fix
I'm closing this as won't fix.
The real fix should be to update the the unit tests for KMSClientProvider to be
more complete to actually cover the code and it's use cases and/or TestKMS
should be fixed to actually follow the intended usages.
> Patches for KMS should test kms-server in precommit as well
> -----------------------------------------------------------
>
> Key: YETUS-264
> URL: https://issues.apache.org/jira/browse/YETUS-264
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
> Reporter: Wei-Chiu Chuang
>
> In HADOOP-12559, a patch was made for
> hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/crypto/key/kms/KMSClientProvider.java
> However, the precommit validation did not run tests in kms-server, which
> happens to use KMSClientProvider. Hence, it did not capture a test failure in
> TestKMS (which is in kms-server) (See HADOOP-12682 too)
> I suppose a change in Hadoop personality is needed to fix this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
