Skip to content

[BEAM-1978] Avoid repackaging bigtable classes in dataflow runner.#2541

Closed
rangadi wants to merge 1 commit into
apache:masterfrom
rangadi:fix_repackage
Closed

[BEAM-1978] Avoid repackaging bigtable classes in dataflow runner.#2541
rangadi wants to merge 1 commit into
apache:masterfrom
rangadi:fix_repackage

Conversation

@rangadi
Copy link
Copy Markdown
Contributor

@rangadi rangadi commented Apr 14, 2017

Dataflow bundled jar does not need to repackage bigtable classes. This repackaging was probably never required in Apache Beam. This didn't affect before BEAM-1722 (PR #2503) since it was a test dependency. Now it is a compile time dependency.

This can mess up classes when a project depends both on google-platform IOs and dataflow runner.

@rangadi
Copy link
Copy Markdown
Contributor Author

rangadi commented Apr 14, 2017

+R: @dhalperi @iemejia

@dhalperi
Copy link
Copy Markdown
Contributor

LGTM

@rangadi
Copy link
Copy Markdown
Contributor Author

rangadi commented Apr 14, 2017

An integration test that was failing earlier passes now.

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage decreased (-0.01%) to 70.457% when pulling 84b7691 on rangadi:fix_repackage into eea96ff on apache:master.

@asfbot
Copy link
Copy Markdown

asfbot commented Apr 14, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/9546/
--none--

@asfgit asfgit closed this in cf9ac45 Apr 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants