beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-939) New credentials code broke Dataflow runner
Date Tue, 08 Nov 2016 04:01:58 GMT


ASF GitHub Bot commented on BEAM-939:

GitHub user lukecwik opened a pull request:

    [BEAM-939] Use the credentials from GcpOptions instead of relying on BigtableOptions

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [x] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [x] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [x] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    This allows for us to create a version of the service depending on the PipelineOptions
passed in at this time. This uses a function which takes in the contextual PipelineOptions
and creates a service from it allowing us to not serialize the Credentials within the BigtableOptions.

You can merge this pull request into a Git repository by running:

    $ git pull beam939

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1308
commit 5fd9cdc0c843cf126ce0f2e6c6c7563471d6b335
Author: Luke Cwik <>
Date:   2016-11-08T03:37:42Z

    [BEAM-939] Use the credentials from GcpOptions instead of relying on the BigtableOptions
to provide them.


> New credentials code broke Dataflow runner
> ------------------------------------------
>                 Key: BEAM-939
>                 URL:
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-gcp
>    Affects Versions: Not applicable
>            Reporter: Daniel Halperin
>            Assignee: Luke Cwik
>            Priority: Minor
>             Fix For: 0.4.0-incubating
> {code}
> java.lang.NoSuchMethodError:;)Lcom/google/auth/oauth2/GoogleCredentials;
> 	at
> 	at
> 	at
> 	at<init>(
> 	at
> 	at$Read.validate(
> 	at$Read.validate(
> 	at org.apache.beam.sdk.Pipeline.applyInternal(
> 	at org.apache.beam.sdk.Pipeline.applyTransform(
> 	at org.apache.beam.sdk.values.PBegin.apply(
> 	at org.apache.beam.sdk.Pipeline.apply(
> 	at
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> 	at java.lang.reflect.Method.invoke(
> 	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(
> 	at
> 	at org.junit.runners.model.FrameworkMethod.invokeExplosively(
> 	at org.junit.internal.runners.statements.InvokeMethod.evaluate(
> 	at org.junit.runners.ParentRunner.runLeaf(
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(
> 	at org.junit.runners.ParentRunner$
> 	at org.apache.maven.surefire.junitcore.pc.Scheduler$
> 	at java.util.concurrent.Executors$
> 	at
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(
> 	at java.util.concurrent.ThreadPoolExecutor$
> 	at
> {code}

This message was sent by Atlassian JIRA

View raw message