partition-separator does not take effect in storage sink

[CharlesCheung96]

What did you do?

1. create changefeed with the following configuration:

   "sink_uri": "s3://tmp/ticdc-cloud-storage-test/table-scheduling-test&force-path-style=true",
    "sink": {
      "protocol": "csv",
      "schema_registry": "",
      "csv": {
        "delimiter": ",",
        "quote": "\"",
        "null": "\\N",
        "include_commit_ts": true
      },
      "column_selectors": null,
      "transaction_atomicity": "",
      "encoder_concurrency": 16,
      "terminator": "\n",
      "date_separator": "day",
      "enable_partition_separator": true
    }

2. create partition table:

 CREATE TABLE `tp1` (
  `id` int(11) NOT NULL,
  `idx` int(11) DEFAULT NULL,
  PRIMARY KEY (`id`) /*T![clustered_index] CLUSTERED */
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin
PARTITION BY RANGE (`id`)
(PARTITION `p0` VALUES LESS THAN (5),
 PARTITION `p1` VALUES LESS THAN (10),
 PARTITION `p3` VALUES LESS THAN (2010))

What did you expect to see?

Output event to diffrent path

What did you see instead?

The partition-separator does not take effect.

  "task_status": [
    {
      "capture_id": "c3eb9195-09a0-4969-9f4b-8a15b75fee3f",
      "table_ids": [
        1046
      ],
      "table_operations": null
    },
    {
      "capture_id": "e4678e59-8704-4ed0-99e4-d564f3680fa0",
      "table_ids": [
        1045
      ],
      "table_operations": null
    },
    {
      "capture_id": "0432c232-8d96-4d5a-9df1-35c25436f359",
      "table_ids": [
        1044
      ],
      "table_operations": null
    }

Versions of the cluster

Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):

(paste TiDB cluster version here)

Upstream TiKV version (execute tikv-server --version):

(paste TiKV version here)

TiCDC version (execute cdc version):

master

[fubinzh]

/severity critical

[Rustin170506]

/assign

[nongfushanquan]

/label affects-6.5