flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3695) ValueArray types
Date Wed, 20 Jul 2016 14:14:20 GMT

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

Stephan Ewen commented on FLINK-3695:
-------------------------------------

Makes sense.

You can probably still get started with these ValueArrayTypes, defining the type, the serializer,
and the type information. That is the same, no matter where the types go.

To make the type info available: Do you think it helps to first have the generic extension
mechanism? Then we could simply allow people to add these types in libraries, and gradually
move core types to the core.

You can probably still go ahead using our custom type info by using the {{.returns(...)}}
method, or the {{ResultTypeQueryable}} interface, even without the type being added to core,
or the extension mechanism being in place.


> ValueArray types
> ----------------
>
>                 Key: FLINK-3695
>                 URL: https://issues.apache.org/jira/browse/FLINK-3695
>             Project: Flink
>          Issue Type: New Feature
>          Components: Type Serialization System
>    Affects Versions: 1.1.0
>            Reporter: Greg Hogan
>            Assignee: Greg Hogan
>            Priority: Minor
>
> Flink provides mutable {{Value}} type implementations of Java primitives along with efficient
serializers and comparators. It would be useful to have corresponding {{ValueArray}} implementations
backed by primitive rather than object arrays, along with an {{ArrayableValue}} interface
tying a {{Value}} to its {{ValueArray}}.



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

Mime
View raw message