-
Notifications
You must be signed in to change notification settings - Fork 4.5k
MySQL Connector - Access denied error but completed as successful job sync #4236
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
Comments
@marcosmarxm @sherifnada this is pretty important. Have you guys seen other instances of this? |
@jrhizor and I are seeing instances for snowflake where the sync job actually fails with the following error but the job is still marked as successful.
|
Second bug we found: check connection succeeds even though the wrong warehouse is added. |
@danieldiamond is possible to set a local csv/json and try to reproduce the error with other destination? Just to validate is a error with Snowflake. |
Unable to find logs from original job. but running into same issue but the root cause is different now. CDC job appears to be successful but is not picking up new data...
DescriptionThis is a CDC job. It was running successfully for a few days, then the credentials were removed so it correctly failed LOG
|
closed in #4617 |
Expected Behavior
If the credentials for a MySQL source no longer have permissions to access the source database, the job sync should fail.
Current Behavior
The job sync receives an error
and yet the job concludes as a successful job sync.
Logs
Uploading logs-1243-0.txt…
Steps to Reproduce
source
with working credentialssource
database and rerun syncSeverity of the bug for you
Medium
Airbyte Version
v0.26.1-alpha
Connector Version (if applicable)
MySQL
0.3.7
Snowflake
0.3.9
Additional context
Environment, version, integration...
The text was updated successfully, but these errors were encountered: