[ 
https://issues.apache.org/jira/browse/FLINK-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nico Kruber updated FLINK-5576:
-------------------------------
    Description: KvStateRequestSerializer#deserializeValue and 
KvStateRequestSerializer#deserializeList both deserialize a given byte array. 
This is used by clients and unit tests and it is fair to assume that these byte 
arrays represent a complete value since we do not offer a method to continue 
reading from the middle of the array anyway. Therefore, we can treat unconsumed 
bytes as errors, e.g. from a wrong serializer being used.  (was: 
KvStateRequestSerializer#deserializeValue and 
KvStateRequestSerializer#deserializeList both deserialize a given byte array. 
This is used by clients and unit tests and it is fair to assume that these byte 
arrays represent a complete value since we do not offer a method to continue 
reading form the middle of the array anyway. Therefore, we can treat unconsumed 
bytes as errors, e.g. from a wrong serializer being used.)

> extend deserialization functions of KvStateRequestSerializer to detect 
> unconsumed bytes
> ---------------------------------------------------------------------------------------
>
>                 Key: FLINK-5576
>                 URL: https://issues.apache.org/jira/browse/FLINK-5576
>             Project: Flink
>          Issue Type: Improvement
>          Components: Queryable State
>    Affects Versions: 1.2.0
>            Reporter: Nico Kruber
>            Assignee: Nico Kruber
>            Priority: Minor
>
> KvStateRequestSerializer#deserializeValue and 
> KvStateRequestSerializer#deserializeList both deserialize a given byte array. 
> This is used by clients and unit tests and it is fair to assume that these 
> byte arrays represent a complete value since we do not offer a method to 
> continue reading from the middle of the array anyway. Therefore, we can treat 
> unconsumed bytes as errors, e.g. from a wrong serializer being used.



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

Reply via email to