You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
we're getting this error interfaceToColumnValue failed for column 'end_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 that
probably 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:
I am sorry to hear that you are running into the issues.
I was able to reproduce the error. When the backup is in creating status, we will not get the end_time value from the APIs we use in this table. Once the backup has been completed, we will get that value.
The column type of the column end_time is TIMESTAMP. While steampie parses a null value to TIMESTAMP, we get the error.
I have raised a PR with the fixes by addressing this issue. Hopefully, the issue will be resolved with the fix.
It would be great if you wanted to give it a try and share your feedback in the PR branch.
Describe the bug
we're getting this error interfaceToColumnValue failed for column 'end_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 that
probably 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: