Mailing-List: contact dev-help@hama.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hama.apache.org
Date: Mon, 13 May 2013 08:51:15 +0000 (UTC)
From: "Edward J. Yoon (JIRA)" <jira@apache.org>
To: dev@hama.apache.org
Message-ID: <JIRA.12647255.1368427556936.308710.1368435075528@arcas>
In-Reply-To: <JIRA.12647255.1368427556936@arcas>
References: <JIRA.12647255.1368427556936@arcas>
Subject: [jira] [Commented] (HAMA-758) Send message to non-exist vertex
 makes the job fail.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Edward J. Yoon commented on HAMA-758:
-------------------------------------

Not long time ago, one of Hama committers added repair function for the same problem HAMA-571. I don't remember why he removed it again, but I think they simply can be ignored.
                
> Send message to non-exist vertex makes the job fail.
> ----------------------------------------------------
>
>                 Key: HAMA-758
>                 URL: https://issues.apache.org/jira/browse/HAMA-758
>             Project: Hama
>          Issue Type: Wish
>          Components: graph
>    Affects Versions: 0.6.1
>            Reporter: MaoYuan Xian
>            Priority: Minor
>
> In graph computing, when sends message to non-exist vertex, job will fail. The problem triggered from iterate method of org.apache.hama.graph.GraphJobCounter.
> Un-completed graph input exists in the real world. Should we ignore these messages sent to non-exist vertext? Or, should we add the mechanism, adds the additional vertex when Vertex.addEdge called?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira