You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2018/01/19 00:27:01 UTC
[jira] [Resolved] (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:all-tabpanel ]
Todd Lipcon resolved KUDU-2254.
-------------------------------
Resolution: Invalid
Fix Version/s: n/a
Discussion on https://gerrit.cloudera.org/#/c/9004/ indicates this isn't really necessary
> 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
> Assignee: Hao Hao
> Priority: Major
> Fix For: n/a
>
>
> 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
(v7.6.3#76005)