[ 
https://issues.apache.org/jira/browse/BAHIR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16751051#comment-16751051
 ] 

ASF GitHub Bot commented on BAHIR-141:
--------------------------------------

GitHub user lukasz-antoniak opened a pull request:

    https://github.com/apache/bahir/pull/82

    [BAHIR-141] Support GCP JSON key type as binary array

    JIRA ticket: https://issues.apache.org/jira/browse/BAHIR-141.
    Original PR: https://github.com/apache/bahir/pull/53.

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

    $ git pull https://github.com/lukasz-antoniak/bahir BAHIR-141

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

    https://github.com/apache/bahir/pull/82.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 #82
    
----
commit 32594e006a9caa764237ba64477e12de167b294e
Author: Lukasz Antoniak <lukasz.antoniak@...>
Date:   2019-01-24T12:06:57Z

    [BAHIR-141] Support GCP JSON key type as binary array

----


> Support for Array[Byte] in SparkGCPCredentials.jsonServiceAccount
> -----------------------------------------------------------------
>
>                 Key: BAHIR-141
>                 URL: https://issues.apache.org/jira/browse/BAHIR-141
>             Project: Bahir
>          Issue Type: Improvement
>          Components: Spark Streaming Connectors
>    Affects Versions: Spark-2.0.2, Spark-2.1.1, Spark-2.2.0
>            Reporter: Ankit Agrahari
>            Priority: Minor
>             Fix For: Spark-2.0.2, Spark-2.2.0
>
>
> Existing implementation of SparkGCPCredentials.jsonServiceAccount has only 
> support for reading the credential file from given path in config(i.e local 
> path). If developer does not have access to worker node it makes easy for 
> developer to add the byte array of json service file rather than path(which 
> will not be available on worker node and will lead to FileNotFound 
> Exaception)from the machine where driver is submitting job from.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to