[
https://issues.apache.org/jira/browse/BEAM-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16206593#comment-16206593
]
ASF GitHub Bot commented on BEAM-3029:
--------------------------------------
GitHub user chamikaramj opened a pull request:
https://github.com/apache/beam/pull/3998
[BEAM-3029] Sets user agent in BigTableIO.Read.getBigTableService().
Cherry-picking this commit to 2.2.0 release branch.
Follow this checklist to help us incorporate your contribution quickly and
easily:
- [ ] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/projects/BEAM/issues/) filed for the
change (usually before you start working on it). Trivial changes like typos do
not require a JIRA issue. Your pull request should address just this issue,
without pulling in other changes.
- [ ] Each commit in the pull request should have a meaningful subject
line and body.
- [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA
issue.
- [ ] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [ ] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will be performed on your pull request automatically.
- [ ] If this contribution is large, please file an Apache [Individual
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
---
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chamikaramj/beam
bigtable_read_it_fix_cerrypick
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/3998.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3998
----
commit 25cab6be8d763a03d2a37f0647698cba79df6ac5
Author: [email protected] <[email protected]>
Date: 2017-10-16T07:50:03Z
Sets user agent in BigTableIO.Read.getBigTableService().
----
> BigTable integration tests failing on Dataflow: UserAgent must not be empty
> ---------------------------------------------------------------------------
>
> Key: BEAM-3029
> URL: https://issues.apache.org/jira/browse/BEAM-3029
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Reporter: Kenneth Knowles
> Assignee: Chamikara Jayalath
> Priority: Blocker
> Fix For: 2.2.0
>
>
> https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/4963/org.apache.beam$beam-runners-google-cloud-dataflow-java/testReport/junit/org.apache.beam.sdk.io.gcp.bigtable/BigtableReadIT/testE2EBigtableRead/
> {code}
> java.lang.IllegalArgumentException: UserAgent must not be empty or null
> at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:122)
> at
> com.google.cloud.bigtable.grpc.BigtableSession.<init>(BigtableSession.java:233)
> at
> org.apache.beam.sdk.io.gcp.bigtable.BigtableServiceImpl.tableExists(BigtableServiceImpl.java:77)
> at
> org.apache.beam.sdk.io.gcp.bigtable.BigtableIO$Read.validate(BigtableIO.java:351)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
