You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2016/02/18 18:41:18 UTC

[jira] [Commented] (TINKERPOP-1162) Add VertexProgram.getTransientComputeKeys() for removing scratch-data.

    [ https://issues.apache.org/jira/browse/TINKERPOP-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152700#comment-15152700 ] 

Marko A. Rodriguez commented on TINKERPOP-1162:
-----------------------------------------------

We will also want {{VertexProgram.getTransientMemoryKeys()}}.

> Add VertexProgram.getTransientComputeKeys() for removing scratch-data.
> ----------------------------------------------------------------------
>
>                 Key: TINKERPOP-1162
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1162
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.1.0-incubating
>            Reporter: Marko A. Rodriguez
>            Assignee: Marko A. Rodriguez
>              Labels: breaking
>             Fix For: 3.2.0-incubating
>
>
> When you run a PageRankVertexProgram or a PeerPressureVertexProgram, you have an {{edgeCount}} property which is used for determining the weight distribution. This is just some "scratch pad data." We need a way to tell the GraphComputer which properties are "scratch pad" and thus, delete them before outputting the `ComputerResult`.
> I propose:
> {code}
> Set<String> VertexProgram.getTransientComputeKeys()
> {code}
> We can have a default that returns {{Collections.emptySet()}}. This would be breaking as the GraphComputer provider will need to handle dropping such properties. This, of course, will be verified in a {{GraphComputerTest.shouldSupportTransientProperties()}}.



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