-
Notifications
You must be signed in to change notification settings - Fork 27
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
gcp_sql_backup table is throwing interfaceToColumnValue failed for column 'start_time' error #535
Comments
@ParthaI i created this issue, because is continue happening |
Hello @jeffreymp17, I hope this message finds you well. I am writing to sincerely apologize for the recurring issue you've been experiencing recently. I understand how frustrating and inconvenient this must be for you, and I want to assure you that resolving this matter is our top priority. After implementing the recent bug fix for the I apologize for the oversight in not running the query with the A PR has been raised to address this issue across all TIMESTAMP type columns. I am optimistic that this will resolve any similar issues with these types of columns. Have you observed a similar issue in any columns other than those of the timestamp type? Test Result:
Thank You! |
Thanks @ParthaI for your work, I'll test the plugin to see if everything is working as a expected |
Describe the bug
we're getting this error interfaceToColumnValue failed for column
'start_time'
: found , expected number\n when we try to execute a query from this table gcp_sql_backup it seems in some point in your side the value cannot be casted or something like thatprobably the vlaue cannot be converted in the sql translation
Steampipe version (steampipe -v)
0.21.3
Plugin version (steampipe plugin list)
v0.47.0
To reproduce
Cannot reproduced
but you can make a query to gpc_sql_backup with invalid date or null maybe
Expected behavior
Should return values
Additional context
The text was updated successfully, but these errors were encountered: