[
https://issues.apache.org/jira/browse/OOZIE-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927534#comment-16927534
]
Julia Kinga Marton commented on OOZIE-3542:
-------------------------------------------
[~dionusos], I yesterday [~zsombor] mentioned offline that the
{{SystemErasureCodingPolicies}} is called using reflection, so is not a good
idea to rename it. I think that the test failures are caused by this rename.
Sorry for the confusion.
> 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
> Attachments: OOZIE-3542-2.patch, OOZIE-3542-3.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.2#803003)
