[
https://issues.apache.org/jira/browse/BEAM-8157?focusedWorklogId=310855&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-310855
]
ASF GitHub Bot logged work on BEAM-8157:
----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Sep/19 17:14
Start Date: 11/Sep/19 17:14
Worklog Time Spent: 10m
Work Description: lukecwik commented on issue #9484: [BEAM-8157] Remove
length prefix from state key for Flink's state backend
URL: https://github.com/apache/beam/pull/9484#issuecomment-530476552
The coder for the main input's key should match the coder being chosen for
the state key.
e.g., if the main input coder is `KV<LP<K>, LP<V>>` then the state key coder
should be LP<K> since `encode(LP<K>) != encode(K)` and even if the runner drops
the length prefixing from `encode(LP<K>)`'s bytes, it still may not be equal to
`encode(K)`.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 310855)
Time Spent: 4h 10m (was: 4h)
> [Flink Runner 1.9] State requests return wrong state in timers when encoded
> key is length-prefixed
> --------------------------------------------------------------------------------------------------
>
> Key: BEAM-8157
> URL: https://issues.apache.org/jira/browse/BEAM-8157
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Affects Versions: 2.13.0
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Major
> Fix For: 2.16.0
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> The Flink runner requires the internal key to be encoded without a length
> prefix (OUTER context). The user state request handler exposes a serialized
> version of the key to the Runner. This key is encoded with the NESTED context
> which may add a length prefix. We need to convert it to OUTER context to
> match the Flink runner's key encoding.
> So far this has not caused the Flink Runner to behave incorrectly. However,
> with the upcoming support for Flink 1.9, the state backend will not accept
> requests for keys not part of any key group/partition of the operator. This
> is very likely to happen with the encoding not being consistent.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
