[
https://issues.apache.org/jira/browse/GIRAPH-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13902119#comment-13902119
]
Hudson commented on GIRAPH-848:
-------------------------------
ABORTED: Integrated in Giraph-trunk-Commit #1417 (See
[https://builds.apache.org/job/Giraph-trunk-Commit/1417/])
GIRAPH-848: Allowing plain computation with types being configurable (ikabiljo
via majakabiljo) (majakabiljo:
http://git-wip-us.apache.org/repos/asf?p=giraph.git&a=commit&h=9a232d185eb97a523359e2e2e73a869a4af15a85)
* giraph-core/src/test/java/org/apache/giraph/master/TestSwitchClasses.java
* CHANGELOG
* giraph-core/src/main/java/org/apache/giraph/master/SuperstepClasses.java
*
giraph-core/src/main/java/org/apache/giraph/conf/ImmutableClassesGiraphConfiguration.java
* giraph-core/src/main/java/org/apache/giraph/master/MasterCompute.java
> Allowing plain computation with types being configurable
> --------------------------------------------------------
>
> Key: GIRAPH-848
> URL: https://issues.apache.org/jira/browse/GIRAPH-848
> Project: Giraph
> Issue Type: Improvement
> Components: lib
> Affects Versions: 1.1.0
> Reporter: Igor Kabiljo
> Attachments: giraph-848.txt
>
>
> All types are configurable via VERTEX_ID_CLASS and other constants in
> GiraphConstants, but they are still required to match Computation types
> (unless code is JYthon).
> It should be allowed to pass, if provided types are subtypes of Computation
> types.
> Also it should be possible to change incoming and outgoing message classes,
> without need to have explicit computation class with appropriate compile time
> defined types.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
