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

[Feature][chunjun-connector-jdbc-base] when custom sql is not empty,all column type need to be set in config #1284

Closed
3 tasks done
liumengkai opened this issue Sep 26, 2022 · 0 comments · Fixed by #1292
Closed
3 tasks done
Labels
feature-request this is a feature requests on the product

Comments

@liumengkai
Copy link
Contributor

liumengkai commented Sep 26, 2022

Search before asking

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

Description

If I have 50 columns and 1 column join from other table to sync ,then I need to set custom sql,and when custom sql is set all columns type(51) need to be set in config , acturally most of them can be read from jdbc metadata

Does this need to be update or It's already what we want.

Use case

No response

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@liumengkai liumengkai added the feature-request this is a feature requests on the product label Sep 26, 2022
@liumengkai liumengkai changed the title [Feature][chunjun-connector-jdbc-base] adapt part of columns select [Feature][chunjun-connector-jdbc-base] when custom sql is not empty,all column type need to be set in config Sep 28, 2022
Paddy0523 added a commit to Paddy0523/chunjun that referenced this issue Sep 30, 2022
@Paddy0523 Paddy0523 linked a pull request Sep 30, 2022 that will close this issue
9 tasks
FlechazoW pushed a commit that referenced this issue Oct 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request this is a feature requests on the product
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant