[jira] [Updated] (TINKERPOP-1141) HadoopRemoteAcceptor is overly complicated. Simplify with ComputerResult as a SideEffect in OLAP Traversal.

["stephen mallette (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TINKERPOP-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette updated TINKERPOP-1141:
----------------------------------------
    Fix Version/s:     (was: 3.2.6)
                   3.2.7

> HadoopRemoteAcceptor is overly complicated. Simplify with ComputerResult as a SideEffect in OLAP Traversal.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: TINKERPOP-1141
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1141
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: hadoop, process
>    Affects Versions: 3.1.0-incubating
>            Reporter: Marko A. Rodriguez
>             Fix For: 3.2.7
>
>
> {{HadoopRemoteAcceptor}} is overly complicated. I think that instead of making {{ComputerResult}} a value in the Console, we should just add {{ComputerResult}} to the OLAP {{Traversal}}.
> {code}
> t = g.V().out().count()
> result = t.getSideEffects().get('~computerResult')
> {code}
> For most people, they will never use this as computer result memory is already in the sideEffects. However, {{ComputerResult}} also has other information like iteration, runtime, and graph.



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