You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2018/06/01 12:02:00 UTC

[jira] [Closed] (TINKERPOP-1966) pageRank() and peerPressure() step should better respect halted traversers

     [ https://issues.apache.org/jira/browse/TINKERPOP-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette closed TINKERPOP-1966.
---------------------------------------
    Resolution: Not A Problem

I created this in error. The filter in front of the {{pageRank()}} and {{peerPressure()}} is only meant to specify the initial vertices to be used in the algorithm and not to specify the ongoing filter within the algorithm itself. That filter should be supplied to the algorithm itself.

> pageRank() and peerPressure() step should better respect halted traversers
> --------------------------------------------------------------------------
>
>                 Key: TINKERPOP-1966
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1966
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: process
>    Affects Versions: 3.2.9
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>            Priority: Major
>
> {{pageRank()}} and {{peerPressure()}} both fail to completely respect halted traversers so that the results of queries that do this:
> {code}
> g.V().hasLabel('person').pageRank()
> {code}
> don't return the right result. In the above case, the initial rank assigned respects halted traversers (i.e. those still part of the traversal after the {{hasLabel()}} filter) but the future iterations do not.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)