[
https://issues.apache.org/jira/browse/SPARK-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240083#comment-14240083
]
Ryan Despain commented on SPARK-3477:
-------------------------------------
Question concerning the "privatization" of a few of these classes. I think the
assumption that no Spark application will directly need access to those, a
remote app wanting to launch a Spark application to yarn could use it.
Our use case is one that we have a clustered Java application that needs to be
able to launch our Spark application. Instead of doing some nasty Java ->
System -> Bash stuff to call spark-submit, we opted to just implement this in
Java making some simple calls to the Client class in spark-yarn.
Now, certainly this use case may be a dumb one and if anyone has any advice on
doing this better we are very open to this. But for now, I would like to ask if
we could undo the privatization of Client, ClientArguments and the others
affected by this story.
> Clean up code in Yarn Client / ClientBase
> -----------------------------------------
>
> Key: SPARK-3477
> URL: https://issues.apache.org/jira/browse/SPARK-3477
> Project: Spark
> Issue Type: Sub-task
> Components: YARN
> Affects Versions: 1.1.0
> Reporter: Andrew Or
> Assignee: Andrew Or
> Fix For: 1.2.0
>
>
> With the addition of new features and supporting multiple versions of yarn
> the code has become cumbersome and could use some clean. We should add
> comments and update to follow the new style guilines also.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
