[
https://issues.apache.org/jira/browse/FLINK-23707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther closed FLINK-23707.
--------------------------------
Fix Version/s: 1.14.0
Resolution: Fixed
Fixed in 1.14.0: 3e62364b1b0d6df9553220dc197ace58c546d544
> Use consistent managed memory weights for StreamNode
> ----------------------------------------------------
>
> Key: FLINK-23707
> URL: https://issues.apache.org/jira/browse/FLINK-23707
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
> Reporter: Timo Walther
> Assignee: Timo Walther
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> Managed memory that is declared on transformations via
> {{Transformation#declareManagedMemoryUseCaseAtOperatorScope(ManagedMemoryUseCase
> managedMemoryUseCase, int weight)}} should be declared using a weight.
> Usually, a weight should be some kind of factor, however, in the table
> planner it is used a kibi byte value. This causes issues on the DataStream
> API side that sets it to {{1}} in
> {{org.apache.flink.streaming.runtime.translators.BatchExecutionUtils#applyBatchExecutionSettings}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
