[
https://issues.apache.org/jira/browse/TEZ-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated TEZ-2924:
-----------------------------
Attachment: TEZ-2924.5.patch
bq. This goes wrong if the shims end up being shipped independently, or
multiple of them end up on the clsaspath - which is a bad install, but we don't
have a way of detecting this.
We do know if more than one provider matches against a given hadoop version.
Current code breaks out of loop on first hit. We could cycle through all and
error out if more than 1 match.
I dont have a strong opinion on either approach. The latter approach means we
catch misbehavior, the former will work but may have unintentional consequences
on a bad setup.
> Framework for Hadoop shims
> --------------------------
>
> Key: TEZ-2924
> URL: https://issues.apache.org/jira/browse/TEZ-2924
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Hitesh Shah
> Assignee: Hitesh Shah
> Attachments: TEZ-2924.2.patch, TEZ-2924.3.patch, TEZ-2924.4.patch,
> TEZ-2924.5.patch, TEZ-2924.wip.1.patch
>
>
> As Hadoop creates a matrix of which versions support what features, Tez will
> need a shim to be cross-compatible and make use of various fixes/features as
> and when possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
