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.

Sign up for GitHub

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

Jump to bottom

Introduce a separate SQL module for shading the dependencies. #87

Open
hackergin opened this issue Apr 22, 2023 · 1 comment
Open

Introduce a separate SQL module for shading the dependencies. #87

hackergin opened this issue Apr 22, 2023 · 1 comment

Comments

@hackergin
Copy link

hackergin commented Apr 22, 2023 •
edited
Loading

By default, the rocketmq-flink jar file contains too many unnecessary dependencies (flink-core/flink-runtime/flink-client/flink-avro/flink-streaming-java/powermock/logback ......)that can easily lead to dependency conflicts.

In the default connector module, we should not perform shading, and we should introduce a separate SQL module for shading the required dependencies. We need to relocate the shaded jar files to avoid conflicts.
@lizhimins
Copy link
Member

lizhimins commented Sep 11, 2023 •
edited
Loading

Great

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lizhimins @hackergin