Skip to content
New issue

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

Can't start changefeed for azure storage sink with sink-uri azure://xxx #7724

Closed
fubinzh opened this issue Nov 25, 2022 · 1 comment · Fixed by #7547
Closed

Can't start changefeed for azure storage sink with sink-uri azure://xxx #7724

fubinzh opened this issue Nov 25, 2022 · 1 comment · Fixed by #7547
Labels
area/ticdc Issues or PRs related to TiCDC. severity/moderate type/bug The issue is confirmed as a bug.

Comments

@fubinzh
Copy link

fubinzh commented Nov 25, 2022

What did you do?

  1. Start CDC changefeed, specify sink-uri azure://xxx

What did you expect to see?

Start storage sink successful

What did you see instead?

Failed to create changefeed with sink-uri azure://xxx:

bash-5.1# /cdc  cli  changefeed  create "--server=127.0.0.1:8301" "--sink-uri=azure://test/storageSink1125?xxx" "--changefeed-id=test1" "--config=/tmp/changefeed.toml"
Error: [CDC:ErrSinkURIInvalid]sink uri invalid 'protocol csv is incompatible with azure scheme'

And it is OK to create changefeed with sink-uri azblob://xxx

Versions of the cluster

bash-5.1# /cdc version
Release Version: v6.5.0-alpha
Git Commit Hash: e0bce5e
Git Branch: heads/refs/tags/v6.5.0-alpha
UTC Build Time: 2022-11-24 11:06:43
Go Version: go version go1.19.3 linux/amd64
Failpoint Build: false

@fubinzh fubinzh added area/ticdc Issues or PRs related to TiCDC. type/bug The issue is confirmed as a bug. labels Nov 25, 2022
@fubinzh
Copy link
Author

fubinzh commented Nov 25, 2022

/severity moderate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ticdc Issues or PRs related to TiCDC. severity/moderate type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants