You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Jingsong Lee (Jira)" <ji...@apache.org> on 2022/07/20 10:23:00 UTC

[jira] [Comment Edited] (FLINK-28482) num-sorted-run.stop-trigger introduced a unstable merging

    [ https://issues.apache.org/jira/browse/FLINK-28482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568969#comment-17568969 ] 

Jingsong Lee edited comment on FLINK-28482 at 7/20/22 10:22 AM:
----------------------------------------------------------------

master: 4cb870b74662fc22ea25fbc29cacf0b14f78a4bf
release-0.2: 95bb7a54d62e6b02492d33381cfb9d73ee2665fe


was (Author: lzljs3620320):
master: 4cb870b74662fc22ea25fbc29cacf0b14f78a4bf

> num-sorted-run.stop-trigger introduced a unstable merging
> ---------------------------------------------------------
>
>                 Key: FLINK-28482
>                 URL: https://issues.apache.org/jira/browse/FLINK-28482
>             Project: Flink
>          Issue Type: Bug
>          Components: Table Store
>            Reporter: Jingsong Lee
>            Assignee: Nicholas Jiang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: table-store-0.2.0
>
>
> We have introduced the num-sorted-run.stop-trigger. The default value is 10.
> This means that the maximum number of runs generated is 10, and 10 runs may be merged at the same time during compaction or read.
> Reading 10 ORC files at the same time may lead to OOM.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)