[BEAM-111] Move WritableCoder to hadoop-common#2118
Conversation
|
R: @amitsela |
|
Refer to this link for build results (access rights to CI server needed): |
| </exclusion> | ||
| </exclusions> | ||
| </dependency> | ||
| <dependency> |
| <description>Library to add shared Hadoop classes among Beam IOs.</description> | ||
|
|
||
| <dependencies> | ||
| <dependency> |
There was a problem hiding this comment.
Is this being introduced for the first time because of WritableCoder moving into hadoop-common ? I guess because of Coder, right ?
There was a problem hiding this comment.
Yes, that's the reason, do you think this is ok (considering that the other libraries depending on this one probably will have the same dependency) ?
There was a problem hiding this comment.
It shouldn't matter since they all bring the same dependency, and I believe that WritableCoder should be in hadoop-common and not hdfs-io,
| <artifactId>beam-sdks-java-core</artifactId> | ||
| </dependency> | ||
|
|
||
| <dependency> |
There was a problem hiding this comment.
Not sure why this is provided, how is this different from the one you removed from io/hdfs ?
There was a problem hiding this comment.
It was not provided, but I am afraid of the version of this leaking into the users of the common library. What do you think should I let it like it was (without the provided) ?
There was a problem hiding this comment.
It was like that in hdfs-io, and if users need to use a different jackson version they should do so explicitly - the Spark runner does that.
14dfc21 to
799cc6f
Compare
|
Ok fixed after comments and rebased. |
|
Refer to this link for build results (access rights to CI server needed): |
799cc6f to
da8b0ad
Compare
|
Rebased because there was a merge issue after changes in master. |
|
Refer to this link for build results (access rights to CI server needed): |
da8b0ad to
5eb2422
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
We are not synchronized because these are different subjects, and this PR is not a blocker for that PR, what I am doing for the moment is just looking for Hadoop classes that are needed in more than one project and moving those to hadoop-common. |
|
Thanks. |
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:
[BEAM-<Jira issue #>] Description of pull requestmvn clean verify. (Even better, enableTravis-CI on your fork and ensure the whole test matrix passes).
<Jira issue #>in the title with the actual Jira issuenumber, if there is one.
Individual Contributor License Agreement.