[
https://issues.apache.org/jira/browse/YETUS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15248773#comment-15248773
]
Colin Patrick McCabe commented on YETUS-222:
--------------------------------------------
When I was reviewing the ISAL patches, I purposely asked that the flags be
{{\-Drequire.isal}} and {{\-Dbundle.isal}}, etc. etc. rather than
{{-Drequire.erasurecode}} so that we could later add liberasurecode or some
other library as an alternative option. I wanted to make it clear that ISAL is
just one implementation of erasure encoding acceleration, and not the only one.
So, [~aw], if you feel strongly about implementing alternate support for
erasure encoding acceleration, please open a Hadoop JIRA and start working on
it.
I agree that it would be bad to break the Yetus build for non-x86
architectures, and I think that the revision I suggested avoids that.
In practice, people who can use ISAL are going to use ISAL, because it is much
faster than the plain Java version. We are not going to rely on Linux
distributions to start shipping libisal, either-- its license is permissive and
it can be bundled with any Hadoop distribution or upstream binary release. It
would be a major gap in Yetus' testing if it didn't cover erasure encoding.
> hadoop: add ISA-L support
> -------------------------
>
> Key: YETUS-222
> URL: https://issues.apache.org/jira/browse/YETUS-222
> Project: Yetus
> Issue Type: Improvement
> Components: Test Patch
> Reporter: Allen Wittenauer
> Assignee: Kai Zheng
> Attachments: YETUS-222-v1.patch, YETUS-222-v2.patch
>
>
> Hadoop personality should support building the native code under Jenkins when
> Docker is invoked.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
