[BEAM-1740] Upgrade to bigtable-client-core 0.9.5.1#2265
[BEAM-1740] Upgrade to bigtable-client-core 0.9.5.1#2265andrewsmartin wants to merge 2 commits intoapache:masterfrom andrewsmartin:master
Conversation
|
Refer to this link for build results (access rights to CI server needed): Failed Tests: 1beam_PreCommit_Java_MavenInstall/org.apache.beam:beam-runners-spark: 1--none-- |
|
R: @dhalperi (welcome back!) |
|
LGTM assuming the tests pass! @tgroh -- any additional changes regarding shading? |
|
@davorbonaci @ssisk @jasonkuster I did not see BigtableITs being run in the precommit where they used to be run. Where are they being run now? |
|
No, this should be fine. We may still not be able to shade the Google Cloud Platform IOs without additional changes as bigtable-client-core still exposes Guava on its API surface in return types (specifically in |
|
BigtableITs are run in postcommit. |
|
So it looks like this commit breaks those tests. @andrewsmartin can you please take a look? It might be there there has been a change in the version of some Bigtable dependency (gRPC, netty, etc.) https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/org.apache.beam$beam-sdks-java-io-google-cloud-platform/2959/testReport/junit/org.apache.beam.sdk.io.gcp.bigtable/BigtableReadIT/testE2EBigtableRead/ |
|
Btw, apparently @andrewsmartin does not have privileges to run the tests without one of the commiters running it for him. Andrew, I'm assuming you have access to your own Bigtable cluster (if you use BigtableIO) -- suggest running the IT manually in your local developer environment. |
|
@dhalperi You're right, there was a version conflict with netty. This version of the bigtable client relies on a class that only exists in |
|
I kicked off https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_MavenInstall/2972/ to run the ITs manually. Thanks @andrewsmartin |
|
Refer to this link for build results (access rights to CI server needed): |
|
Passed! Merged, 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.