tchivs opened a new pull request, #4199:
URL: https://github.com/apache/flink-cdc/pull/4199
## Summary
Allow `table-options` in transform rules to use semicolon (`;`) as the
key/value pair delimiter so option values can safely contain commas (e.g.
`sequence.field=gxsj,jjsj`). Keep comma delimiter for backward compatibility.
## Motivation
Some downstream table options are multi-value and use comma inside the
value. The existing `key1=value1,key2=value2` syntax makes those options
impossible to express reliably.
## Changes
- `SchemaMetadataTransform` parses `table-options` pairs using:
- `;` when present in the string, otherwise `,`
- `split("=", 2)` to avoid breaking values containing `=`
- Docs updated to mention semicolon delimiter for comma-in-value cases.
- New unit tests for the parsing behavior.
## Behavior
- Still supports legacy format:
- `table-options: key1=value1,key2=value2`
- Supports semicolon format (recommended when values contain commas):
- `table-options:
sequence.field=gxsj,jjsj;file-index.range-bitmap.columns=jjsj;file-index.bloom-filter.columns=jjdbh`
- Note: delimiter is chosen by presence of `;` (do not mix `,` and `;` in
the same string).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
