giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitay Joffe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-589) AbstractHiveToVertexValue/Edge/VertexEdges should not require all generic types
Date Tue, 26 Mar 2013 02:49:15 GMT

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

Nitay Joffe commented on GIRAPH-589:
------------------------------------

Yeah it's all because of the DefaultImmutableClassesGiraphConfigurable. I'm fine with this.
                
> AbstractHiveToVertexValue/Edge/VertexEdges should not require all generic types
> -------------------------------------------------------------------------------
>
>                 Key: GIRAPH-589
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-589
>             Project: Giraph
>          Issue Type: Bug
>            Reporter: Alessandro Presta
>            Assignee: Nitay Joffe
>
> The above classes are defined in terms of I, V, E, M, while they would only require two
of them (I, V or I, E).
> I know that it might lead to unchecked casts, but I believe this is still better that
the current version, which breaks composability (what if I want to use the same HiveToVertexValue
type with different edge or message types?).

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

Mime
View raw message