You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Matthias Broecheler (JIRA)" <ji...@apache.org> on 2015/09/17 07:48:45 UTC

[jira] [Created] (TINKERPOP3-846) General In-Memory GraphComputer

Matthias Broecheler created TINKERPOP3-846:
----------------------------------------------

             Summary: General In-Memory GraphComputer
                 Key: TINKERPOP3-846
                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-846
             Project: TinkerPop 3
          Issue Type: Bug
            Reporter: Matthias Broecheler


Implement a generalized In-Memory GraphComputer that can be utilized by any vendor for use cases of small graphs and where performance isn't critical.
This GraphComputer would, similar to the one for TinkerGraph, keep everything in memory. It would rely on the {{graph.vertices()}} method of the underlying graph for access to the data.

Note, this looks likes a duplicate of TINKERPOP3-42. However, the motivation for this ticket is not to develop an efficient GraphComputer or one that can deal with large graphs - just a default implementation. Also, it is not clear why the view would need to copy the entire graph or cache. The view would only need to hold the delta that is being modified by the GraphComputer.

This would be incredibly useful as a utility for vendors to use for small scale graphs where hassle of setting up Hadoop or Spark is just too much.



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