nk-table/flink-table-runtime-blink/src/main/java/org/apache/flink/table/runtime/operators/join/stream/StreamingJoinOperator.java)
in Blink planner. And there're some test cases that failed, such as
AggregateITCase.testGroupBySingleValue.
After debugging, I found the corresponding heap me
e/flink/table/runtime/operators/join/stream/StreamingJoinOperator.java)
in Blink planner. And there're some test cases that failed, such as
AggregateITCase.testGroupBySingleValue.
After debugging, I found the corresponding heap memory for
BinaryRowDataUtil.EMPTY_ROW was changed unexpectedly, from
[0,
AggregateITCase.testGroupBySingleValue.
>>
>> After debugging, I found the corresponding heap memory for
>> BinaryRowDataUtil.EMPTY_ROW was changed unexpectedly, from
>> [0,0,0,0,0,0,0,0]
>> to [3,0,0,0,0,0,0,0], and lead to some records being set to a wrong key.
>&
memory for
BinaryRowDataUtil.EMPTY_ROW was changed unexpectedly, from [0,0,0,0,0,0,0,0]
to [3,0,0,0,0,0,0,0], and lead to some records being set to a wrong key.
However, my mini-batch code doesn't have any low-level operators with
MemorySegment. I only buffered some records (RowData) in
d, such as
AggregateITCase.testGroupBySingleValue.
After debugging, I found the corresponding heap memory for
BinaryRowDataUtil.EMPTY_ROW was changed unexpectedly, from [0,0,0,0,0,0,0,0]
to [3,0,0,0,0,0,0,0], and lead to some records being set to a wrong key.
However, my mini-batch code doesn't have any low-level
