[
https://issues.apache.org/jira/browse/TINKERPOP-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-1141.
---------------------------------------
Resolution: Won't Do
This one is kinda old - not sure that in today's terms i'm seeing how we do
much to help {{HadoopRemoteAcceptor}}. it would be nice to just factor that out
completely but since we can't quite get rid of it due to it's support for
lambdas I'm thinking we're sorta stuck with it anyway. Since we're also trying
to avoid promoting of side-effects perhaps it's best to just leave this one
undone.
> 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
> Priority: Major
>
> {{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
(v7.6.3#76005)
