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][Catalog] Catalog API Upgrade Feature #6774

Open
3 tasks done
Jetiaime opened this issue Apr 29, 2024 · 0 comments
Open
3 tasks done

[Feature][Catalog] Catalog API Upgrade Feature #6774

Jetiaime opened this issue Apr 29, 2024 · 0 comments

Comments

@Jetiaime
Copy link
Contributor

Search before asking

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

Description

I'm rewrting SeaTunnel-Web for some reason, I found that there is not necessary to have datasource in the Web Project, we can just using Catalog instead, but I got some problems when I using Catalog:

  1. jdbc connector is so special that i have to split it to multi connector for different catalog, can we make sure one catalog to one connector? There will be more easy for writing catalog related service.
  2. I cannot get TableSchema when I have unsupported Column Type. There will be better if we just record it in the column and let the user know there cannot be selected.

I'm thinking of making catalog not only for the inside of seatunnel, but as a service that can be requested. So we can cut all the metadata service off and just be a client to seatunnel engine.

Usage Scenario

No response

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant