[FLINK-23707] Use consistent managed memory weights for StreamNode

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.14.0
• Component/s: Table SQL / Planner
• Labels: pull-request-available
• Assignee: Timo Walther
• Reporter: Timo Walther
• Created: 10/Aug/21 10:03
• Updated: 12/Aug/21 13:47
• Resolved: 12/Aug/21 13:47

Description

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.

Issue Links

• links to: GitHub Pull Request #16771