[
https://issues.apache.org/jira/browse/TINKERPOP3-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP3-373:
----------------------------------------
Fix Version/s: 3.0.0.GA
> GraphComputer property persistence options
> ------------------------------------------
>
> Key: TINKERPOP3-373
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-373
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Reporter: Matthias Broecheler
> Assignee: Marko A. Rodriguez
> Fix For: 3.0.0.GA
>
>
> I noticed that the implicit assumption is that element compute keys (and the
> values associated with them during the vertex computer iterations) are
> persisted back into the graph after termination.
> Two thoughts on this:
> 1) There should be an option to disable this. For instance, one might want to
> run PageRank and then run a map-reduce job to determine the 10 hightest
> ranked vertices. If it is required that all PR values are being written back
> into the graph that would become prohibitively expensive on large graphs.
> 2) It should be possible to define which subset of the elementComputeKeys one
> wants to persist back into the graph. For instance, for PR one typically only
> wants the PR value and not the edge-count
> ===> Vertex.getElementComputeKeys() should return a Map<String,Boolean> where
> the boolean value indicates whether the value should be persisted back into
> the graph. If all are false, then nothing is written back as required in (1).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
