GitHub user sihuazhou opened a pull request:

    https://github.com/apache/flink/pull/5993

    [FLINK-9336][state] fix deserialization problem for queryable MapState

    ## What is the purpose of the change
    
    This PR fixes the deserialization problem for queryable MapState. Currently 
MapState use the `userKeyOffset` to skip the userKeyBytes when doing 
deserialization, for queryable state this will bring problem, this PR keeps the 
`userKeyOffset` in every `RocksDBMapEntry` to avoid the deserialization problem 
for queryable MapState.
    
    ## Brief change log
    
      - *Keep the `userKeyOffset` in every `RocksDBMapEntry` to avoid 
deserialization problem in queryable state.*
    
    ## Verifying this change
    
    This change is a trivial rework / code cleanup without any test coverage.
    
    ## Does this pull request potentially affect one of the following parts:
    
      - Dependencies (does it add or upgrade a dependency): (no)
      - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (no)
      - The serializers: (no)
      - The runtime per-record code paths (performance sensitive): (no)
      - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
      - The S3 file system connector: (no)
    
    ## Documentation
    
      - Does this pull request introduce a new feature? (no)


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sihuazhou/flink FLINK-9336

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/5993.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #5993
    
----
commit 7b8443cd3d7f405bed97f00e1542a1004aef9ff8
Author: sihuazhou <summerleafs@...>
Date:   2018-05-11T15:15:07Z

    keep the userKeyOffset in every MapEntry to avoid deserialization problem 
in queryable state.

----


---

Reply via email to