[
https://issues.apache.org/jira/browse/FLINK-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867194#comment-15867194
]
ASF GitHub Bot commented on FLINK-5790:
---------------------------------------
Github user shixiaogang commented on the issue:
https://github.com/apache/flink/pull/3305
@StephanEwen @tillrohrmann I found a problem that is the packages
`ListTypeInfo` and `ListTypeSerializer` locate. Now `ListTypeInfo` is put in
package "org.apache.flink.api.java.typeutils" and `ListSerializer` is put in
package "org.apache.flink.api.common.typeutils.base". But i think it's better
to put "ListTypeInfo" into package "org.apache.flink.api.common.typeinfo". What
do you think?
> Use list types when ListStateDescriptor extends StateDescriptor
> ---------------------------------------------------------------
>
> Key: FLINK-5790
> URL: https://issues.apache.org/jira/browse/FLINK-5790
> Project: Flink
> Issue Type: Improvement
> Reporter: Xiaogang Shi
> Assignee: Xiaogang Shi
>
> Flink keeps the state serializer in {{StateDescriptor}}, but it's the
> serializer of list elements that is put in {{ListStateDescriptor}}. The
> implementation is a little confusing. Some backends need to construct the
> state serializer with the element serializer by themselves.
> We should use an {{ArrayListSerializer}}, which is composed of the serializer
> of the element, in the {{ListStateDescriptor}}. It helps the backend to avoid
> constructing the state serializer.
> If a backend needs customized serialization of the state (e.g.
> {{RocksDBStateBackend}}), it still can obtain the element serializer from the
> {{ArrayListSerializer}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
