-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
JDBC sources: Improve error message when an invalid cursor column is selected #13912
Comments
Sentry issue: CONNECTOR-INCIDENT-MANAGEMENT-8 |
It appears that the user was able to set up an incremental sync with an unsupported field type. |
after #14714 this will be reported with a slightly more informative error message ( Hopefully sentry is able to recognize that as the same stacktrace, but leaving a breadcrumb comment in case it doesn't. |
It would be slightly nicer if |
yeah, that's fair. I updated the issue title and description. It requires a bit of refactoring to get the table+column name down to where the exception is thrown (or maybe to catch the exception where the those names are known?) so going to leave this be for now. |
Agreed, just noting a future ideal. Thanks. |
This started happening again two days ago for another customer |
This connection has a lot of tables, but from the error log, I cannot tell which table is failing. Would be great if the log included the name of the table, name of the field, field value, and as much information about field type and why JDBC driver cannot map it to any known type.
|
Related alpha-beta issue: https://github.com/airbytehq/alpha-beta-issues/issues/164 |
My PR has been approved but the build is failing, the remaining thing is to fix the build and get it merged |
@subodh1810 builds should be OK now |
When a non-sortable column is used as a cursor, we currently produce an error message that isn't super useful (
<column type> can't be used as a cursor
). Ideally, this message should include the table and column names, to assist users in tracking down which stream is causing the problem.Something interesting on this cloud account.
More details: https://docs.google.com/spreadsheets/d/1ja8deCtFHtFVP3QrWELsMpVCMfPB1kz0QfLG1szns1I/edit#gid=408762974
The text was updated successfully, but these errors were encountered: