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

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

Github user ckadner commented on the issue:

    https://github.com/apache/bahir/pull/48
  
    @ire7715 
    
    ```
    [INFO] --- scala-maven-plugin:3.2.2:compile (scala-compile-first) @ 
spark-streaming-pubsub_2.11 ---
    ...
    [INFO] Compiling 3 Scala sources to 
/var/lib/jenkins/workspace/bahir_spark_pr_builder/streaming-pubsub/target/scala-2.11/classes...
    [ERROR] 
/var/lib/jenkins/workspace/bahir_spark_pr_builder/streaming-pubsub/src/main/scala/org/apache/spark/streaming/pubsub/SparkGCPCredentials.scala:20:
 object jackson is not a member of package com.google.api.client.json
    [ERROR] import com.google.api.client.json.jackson.JacksonFactory
    [ERROR]                                   ^
    [ERROR] 
/var/lib/jenkins/workspace/bahir_spark_pr_builder/streaming-pubsub/src/main/scala/org/apache/spark/streaming/pubsub/SparkGCPCredentials.scala:74:
 not found: type JacksonFactory
    [ERROR]     val jsonFactory = new JacksonFactory
    [ERROR]                           ^
    [ERROR] two errors found
    ```


> [PubSub] Make "ServiceAccountCredentials" really broadcastable
> --------------------------------------------------------------
>
>                 Key: BAHIR-122
>                 URL: https://issues.apache.org/jira/browse/BAHIR-122
>             Project: Bahir
>          Issue Type: Improvement
>          Components: Spark Streaming Connectors
>            Reporter: Ire Sun
>
> The origin implementation broadcast the key file path to Spark cluster, then 
> the executor read key file with the broadcasted path. Which is absurd, if you 
> are using a shared Spark cluster in a group/company, you certainly not want 
> to (and have no right to) put your key file on each instance of the cluster.
> If you store the key file on driver node and submit your job to a remote 
> cluster. You would get the following warning:
> {{WARN ReceiverTracker: Error reported by receiver for stream 0: Failed to 
> pull messages - java.io.FileNotFoundException}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to