[
https://issues.apache.org/jira/browse/TINKERPOP-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Xia closed TINKERPOP-1593.
-------------------------------
Resolution: Won't Do
Closing given
[discussion|https://lists.apache.org/thread/om2m0phg25s83529p9w0gldmcxz7578h] -
it can be reopened if there is expectation that there will be active work on
this item.
> TraversalMatrix should be blown out to reduce the amount of work to develop
> and OLAP engine
> -------------------------------------------------------------------------------------------
>
> Key: TINKERPOP-1593
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1593
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.2.3
> Reporter: Marko A. Rodriguez
> Priority: Major
>
> I'm noticing that there is a lot of repeated code in {{GraphComputer}} and
> {{GraphActors}}. Both processing engines rely on a mix of push-based and
> pull-based semantics through the traversal. I believe we can fold alot of
> this code into {{TraversalMatrix}}. In this way, {{TraversalMatrix}} will
> know how to add traversers into their appropriate step. It will know how to
> fetch barriers. It will know how to fast-forward into a traversal and pull
> from there. In short, it will do all the complicated logic that we currently
> have in {{TraversalVertexProgram}} (and {{TraversalActorProgram}}).
> Here is what it should do:
> * {{TraversalMatrix.addTraverser()}}
> * {{TraversalMatrix.setSemantics()}}
> * {{TraversalMatrix.nextTraverser()}}
> * {{TraversalMatrix.nextBarrier()}}
> ...and moving forward.
> * {{TraversalMatrix.setPartition()}}
> The last will make it so that all an OLAP engine needs to do is add
> traversers and what ever comes back, message pass. Super basic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
