We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TiCDC has a one character limitation for CSV delimiter, this will limit users using special characters like hex(FF, FE) as delimiter.
When user specify the delimiter, supports at most 2 characters delimiter.
There is a hard limitation that the delimiter is 1 character, so there is no alternative to workaround this problem.
This is an extension for existing sink to CSV capability, this will give users better capability to customize their CSV format.
The text was updated successfully, but these errors were encountered:
csv: delimiter supports at most 2 characters (#9970)
5480006
close #9969
Some customers use separator like |@| in their env. So we need to relief the restriction further to support 3 characters.
|@|
Sorry, something went wrong.
csv(cdc): delimiter supports at most 3 characters (#10357)
54b518d
ref #9969
zhangjinpeng87
Successfully merging a pull request may close this issue.
Is your feature request related to a problem?
TiCDC has a one character limitation for CSV delimiter, this will limit users using special characters like hex(FF, FE) as delimiter.
Describe the feature you'd like
When user specify the delimiter, supports at most 2 characters delimiter.
Describe alternatives you've considered
There is a hard limitation that the delimiter is 1 character, so there is no alternative to workaround this problem.
Teachability, Documentation, Adoption, Migration Strategy
This is an extension for existing sink to CSV capability, this will give users better capability to customize their CSV format.
The text was updated successfully, but these errors were encountered: