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

[Bug] [Seatunnel-config-sql] No exception for error config #7276

Closed
2 of 3 tasks
dailai opened this issue Jul 26, 2024 · 3 comments
Closed
2 of 3 tasks

[Bug] [Seatunnel-config-sql] No exception for error config #7276

dailai opened this issue Jul 26, 2024 · 3 comments

Comments

@dailai
Copy link
Contributor

dailai commented Jul 26, 2024

Search before asking

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

What happened

There is a comma missing in the configuration, but there is no error in the job, and the database name passed to the sink is not correct
截屏2024-07-26 16 45 20

截屏2024-07-26 16 34 08

SeaTunnel Version

2.3.6

SeaTunnel Config

The jdbc_mysql_source_and_sink_with_multiple_tables.sql in e2e case

Running Command

./bin/seatunnel.sh --config ./config jdbc_mysql_source_and_sink_with_multiple_tables.sql

Error Exception

No exception. But the database name in sink is not right.

Zeta or Flink or Spark Version

No response

Java or Scala Version

No response

Screenshots

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@dailai dailai added the bug label Jul 26, 2024
dailai added a commit to dailai/seatunnel that referenced this issue Jul 26, 2024
@dailai dailai changed the title [Bug] [Seatunnel-confi-sql] No exception for error config [Bug] [Seatunnel-config-sql] No exception for error config Jul 26, 2024
@hailin0 hailin0 closed this as completed Jul 27, 2024
@hailin0 hailin0 reopened this Jul 29, 2024
@hailin0
Copy link
Member

hailin0 commented Jul 29, 2024

cc @rewerma

Copy link

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Aug 29, 2024
Copy link

github-actions bot commented Sep 5, 2024

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.

@github-actions github-actions bot closed this as completed Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants