[
https://issues.apache.org/jira/browse/OOZIE-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927884#comment-16927884
]
Zsombor Gegesy commented on OOZIE-3542:
---------------------------------------
Sorry, I wasn't near to a laptop. I've renamed the test class in patch #4, but
the SystemErasureCodingPolicies unfortunately called from ECPolicyDisabler with
reflection - so it's not obvious that you couldn't change it. When Oozie could
depend on Hadoop 3 directly, the mocking could be much simpler
> 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,
> OOZIE-3542-4.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)
