Mailing-List: contact dev-help@hama.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hama.apache.org
Date: Wed, 20 Feb 2013 12:53:12 +0000 (UTC)
From: "Thomas Jungblut (JIRA)" <jira@apache.org>
To: dev@hama.apache.org
Message-ID: <JIRA.12633070.1361306108385.310284.1361364792937@arcas>
In-Reply-To: <JIRA.12633070.1361306108385@arcas>
References: <JIRA.12633070.1361306108385@arcas>
Subject: [jira] [Updated] (HAMA-735) Tighten the graph API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Thomas Jungblut updated HAMA-735:
---------------------------------

    Attachment: HAMA-735_2.patch

You are completely right, I forgot that there was an interface of the vertex somewhere that contained the types as well. Fixed that in the newest patch.
                
> Tighten the graph API 
> ----------------------
>
>                 Key: HAMA-735
>                 URL: https://issues.apache.org/jira/browse/HAMA-735
>             Project: Hama
>          Issue Type: Improvement
>          Components: graph
>    Affects Versions: 0.6.0
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>             Fix For: 0.6.1
>
>         Attachments: HAMA-735_1.patch, HAMA-735_2.patch
>
>
> Tighten the API by the following improvements:
> - replace the need to provide a new object of vertex parts
> - readState/writeState shouldn't be forced to override (clutters code with empty methods)
> - add preconditions for not supplied readers 
> - generalize the usage of vertex part classes and unify their usage
> - replace unuseful testcases / test methods
> - simplify graph logic by removing repair functionalities
> - formatting + organize of imports
> - add WritableComparable<?> to the vertex ID for efficient merging of vertices and joining of them with messages

--
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