[
https://issues.apache.org/jira/browse/BEAM-8157?focusedWorklogId=309119&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-309119
]
ASF GitHub Bot logged work on BEAM-8157:
----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Sep/19 17:48
Start Date: 09/Sep/19 17:48
Worklog Time Spent: 10m
Work Description: tweise 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-529591807
I'm reasonably sure. But if you tell me that you tested your latest change
with the pipeline in the gist then I can repeat it.
----------------------------------------------------------------
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: 309119)
Time Spent: 3h 50m (was: 3h 40m)
> [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: 3h 50m
> 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)
