You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2015/09/29 00:44:05 UTC

[jira] [Commented] (TINKERPOP3-845) Spark Execution Options

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

Marko A. Rodriguez commented on TINKERPOP3-845:
-----------------------------------------------

Do you have an links/examples? The easiest way to do such things would be through {{Configuration}} given that it doesn't change the TinkerPop APIs.

> Spark Execution Options
> -----------------------
>
>                 Key: TINKERPOP3-845
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-845
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: hadoop
>    Affects Versions: 3.0.1-incubating
>            Reporter: Matthias Broecheler
>            Assignee: Marko A. Rodriguez
>
> In Spark, the user has some control over how the Spark job should be executed. In particular, the user can control if certain RDDs should be cached. In SparkSQL this is exposed via custom SQLish commands to the user. We should investigate if something similar can be done in Gremlin to give the user more control over their job execution.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)