[
https://issues.apache.org/jira/browse/OOZIE-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938437#comment-16938437
]
Kinga Marton commented on OOZIE-3542:
-------------------------------------
Thank you @zsombor for the clarification! The fix looks good to me. Can you
please extend the test with the scenarios when the other two methods are not
supported? As you did for getErasureCodingPolicy method in
{{testServerNotSupportsGetErasureCodingPolicyMethod()}}
> Handle better old Hdfs implementations in ECPolicyDisabler
> ----------------------------------------------------------
>
> Key: OOZIE-3542
> URL: https://issues.apache.org/jira/browse/OOZIE-3542
> Project: Oozie
> Issue Type: Bug
> Components: tools
> Reporter: Zsombor Gegesy
> Assignee: Zsombor Gegesy
> Priority: Major
> Fix For: 5.2.0
>
> Attachments: OOZIE-3542-2.patch, OOZIE-3542-3.patch,
> OOZIE-3542-4.patch, OOZIE-3542-amend-01.patch
>
>
> Currently, ECPolicyDisabler checks if the local hdfs implementation has the
> necessary methods to get and set erasure coding policy. However, if the
> namenode implementation is old, it could throw a
> org.apache.hadoop.ipc.RemoteException with
> RpcErrorCodeProto.ERROR_NO_SUCH_METHOD value in it.
> In this case, ECPolicyDisabler fails, and prevents the installation to
> succeed.
> This case should be handled just like, when erasure coding is not supported.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
