[Bug] [dataquality] when readers":[] As a result, the reader information is empty and the spark task is submitted
Search before asking
- [X] I had searched in the issues and found no similar issues.
What happened
The source table of the production environment and the test environment is inconsistent. This problem occurs when the configuration is imported from the test environment to the production. reader information cannot be obtained, but the data quality task is not detected, so the spark task is submitted. Causes the task to clearly throw an exception, but the final state is successful
What you expected to happen
The source table of the production environment and the test environment is inconsistent. This problem occurs when the configuration is imported from the test environment to the production. reader information cannot be obtained, but the data quality task is not detected, so the spark task is submitted. Causes the task to clearly throw an exception, but the final state is successful
How to reproduce
The source table of the production environment and the test environment is inconsistent. This problem occurs when the configuration is imported from the test environment to the production. reader information cannot be obtained, but the data quality task is not detected, so the spark task is submitted. Causes the task to clearly throw an exception, but the final state is successful
Anything else
The source table of the production environment and the test environment is inconsistent. This problem occurs when the configuration is imported from the test environment to the production. reader information cannot be obtained, but the data quality task is not detected, so the spark task is submitted. Causes the task to clearly throw an exception, but the final state is successful
Version
3.1.x
Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
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.
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.