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

[Feat][connector][oraclelogminer] oracle do not support nchar、nvarchar2 chinese value #1193

Closed
3 tasks done
momisabuilder opened this issue Aug 29, 2022 · 0 comments · Fixed by #1194
Closed
3 tasks done
Assignees
Labels
bug Something isn't working
Projects

Comments

@momisabuilder
Copy link
Contributor

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

[chunjun-connector-oraclelogminer] oracle do not support nchar、nvarchar2 chinese value1

What you expected to happen

1

How to reproduce

1

Anything else

No response

Version

master

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@momisabuilder momisabuilder added the bug Something isn't working label Aug 29, 2022
@FlechazoW FlechazoW added this to To do in v1.12.6 via automation Aug 29, 2022
@chaozwn chaozwn changed the title [chunjun-connector-oraclelogminer] oracle do not support nchar、nvarchar2 chinese value [Feat][chunjun-connector-oraclelogminer] oracle do not support nchar、nvarchar2 chinese value Aug 29, 2022
@chaozwn chaozwn changed the title [Feat][chunjun-connector-oraclelogminer] oracle do not support nchar、nvarchar2 chinese value [Feat][connector][oraclelogminer] oracle do not support nchar、nvarchar2 chinese value Aug 29, 2022
momisabuilder added a commit to momisabuilder/chunjun that referenced this issue Aug 29, 2022
@chaozwn chaozwn linked a pull request Aug 29, 2022 that will close this issue
v1.12.6 automation moved this from To do to Done Aug 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant