You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Will Berkeley (JIRA)" <ji...@apache.org> on 2018/01/09 23:03:00 UTC

[jira] [Commented] (KUDU-2254) Detect and warn about misusage of KuduContext in spark applications

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

Will Berkeley commented on KUDU-2254:
-------------------------------------

We might be able to use [TaskContext|https://spark.apache.org/docs/2.2.0/api/java/org/apache/spark/TaskContext.html] to detect this situation and warn users.

> Detect and warn about misusage of KuduContext in spark applications
> -------------------------------------------------------------------
>
>                 Key: KUDU-2254
>                 URL: https://issues.apache.org/jira/browse/KUDU-2254
>             Project: Kudu
>          Issue Type: Improvement
>          Components: spark
>    Affects Versions: 1.5.0
>            Reporter: Hao Hao
>
> Since KuduContext carries a bunch of information for client connection, such as authentication token, KuduContext should be created in the driver and shared with executors.
> Even if we have put comments for KuduContext class (https://github.com/apache/kudu/blob/master/java/kudu-spark/src/main/scala/org/apache/kudu/spark/kudu/KuduContext.scala#L43), it would be great to provide a way to warn users (e.g Logging) about such behavior since this kind of issues are very subtle to detect.



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