[jira] [Commented] (FLINK-3277) Use Value types in Gelly API

["Gabor Gevay (JIRA)" <ji...@apache.org>]

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

Gabor Gevay commented on FLINK-3277:
------------------------------------

I think that this issue that new heap objects are created when deserializing a Tuple/POJO with a long field, will have a clean solution when we will have code-generation for the serializers. Then fields of primitive types (like long) can be handled specially: the generated code won't call the fieldSerializer, but directly call readLong, and write the result into the field.

> Use Value types in Gelly API
> ----------------------------
>
>                 Key: FLINK-3277
>                 URL: https://issues.apache.org/jira/browse/FLINK-3277
>             Project: Flink
>          Issue Type: Improvement
>          Components: Gelly
>    Affects Versions: 1.0.0
>            Reporter: Greg Hogan
>            Assignee: Greg Hogan
>
> This would be a breaking change so the discussion needs to happen before the 1.0.0 release.
> I think it would benefit Flink to use {{Value}} types wherever possible. The {{Graph}} functions {{inDegrees}}, {{outDegrees}}, and {{getDegrees}} each return {{DataSet<Tuple2<K, Long>>}}. Using {{Long}} creates a new heap object for every serialization and deserialization. The mutable {{Value}} types do not suffer from this issue when object reuse is enabled.
> I lean towards a preference for conciseness in documentation and performance in examples and APIs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)