You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Anderson de Andrade (JIRA)" <ji...@apache.org> on 2016/06/02 22:09:59 UTC
[jira] [Updated] (SPARK-15739) Expose
aggregateMessagesWithActiveSet to users.
[ https://issues.apache.org/jira/browse/SPARK-15739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anderson de Andrade updated SPARK-15739:
----------------------------------------
Description:
The current version of Pregel has some flaws:
* Each iteration expands the lineage, making stages slower as it progresses.
* It uses the deprecated {{mapReduceTriplets}} method, which makes the interface of the sendMsg function different from {{aggregateMessages}}, bringing inconsistencies to the API.
* It enforces an initialization stage that prevents users from having a custom state at the beginning of the process.
It would be fairly trivial to create custom versions of Pregel that would work for many other use cases if {{aggregateMessagesWithActiveSet}} were not a private method.
was:
The current version of Pregel has some flaws:
* Each iteration expands the lineage, making stages slower as it progresses.
* It uses the deprecated {{mapReduceTriplets}} method, which makes the interface of the sendMsg function different from {{aggregateMessages}}, bringing inconsistencies to the API.
* It enforces an initialization tage, preventing users from having a custom state at the beginning of the process.
It would be fairly trivial to create custom versions of Pregel that would work for many other use cases if {{aggregateMessagesWithActiveSet}} were not a private method.
> Expose aggregateMessagesWithActiveSet to users.
> -----------------------------------------------
>
> Key: SPARK-15739
> URL: https://issues.apache.org/jira/browse/SPARK-15739
> Project: Spark
> Issue Type: Improvement
> Components: GraphX
> Affects Versions: 1.6.1
> Reporter: Anderson de Andrade
> Priority: Minor
>
> The current version of Pregel has some flaws:
> * Each iteration expands the lineage, making stages slower as it progresses.
> * It uses the deprecated {{mapReduceTriplets}} method, which makes the interface of the sendMsg function different from {{aggregateMessages}}, bringing inconsistencies to the API.
> * It enforces an initialization stage that prevents users from having a custom state at the beginning of the process.
> It would be fairly trivial to create custom versions of Pregel that would work for many other use cases if {{aggregateMessagesWithActiveSet}} were not a private method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org