You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Lee SeungMin (Jira)" <ji...@apache.org> on 2024/07/02 09:35:00 UTC

[jira] [Created] (FLINK-35740) [mysql] Allow column as chunk key even if not in Primary Keys

Lee SeungMin created FLINK-35740:
------------------------------------

             Summary: [mysql] Allow column as chunk key even if not in Primary Keys
                 Key: FLINK-35740
                 URL: https://issues.apache.org/jira/browse/FLINK-35740
             Project: Flink
          Issue Type: Improvement
          Components: Flink CDC
            Reporter: Lee SeungMin


Change the input chunk key to allow it even if it is not in the primary keys. 

There are cases where the primary key is not a numeric type, such as varchar or varbinary. In this case, the `distributed factor` and `chunk range` may be calculated incorrectly, resulting in one chunk containing many records.

This may cause out of memory in the task manager. 

Actually, in our company, there was a mysql tables that PK is a varbinary column and the above situation occurred.



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