-
Notifications
You must be signed in to change notification settings - Fork 105
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
interface conversion error with cold cache when querying aws_route53_record #1960
Comments
Hello @tinder-tder, thank you for bringing this issue to our attention, and I truly appreciate your engagement with Steampipe. I have successfully replicated the error ( case 1: Using
Case 2: Using
Case 3: Using
I suspect the issue might lie with the FDW or the Steampipe Plugin SDK in terms of query parsing. Consequently, I have submitted a support request to the Steampipe Plugin SDK team, specifically addressing this concern. We can track the issue here: turbot/steampipe-plugin-sdk#702 Thank You! |
@ParthaI Thanks will keep an eye out for the fix! |
Hey @tinder-tder, We are closing this issue because we can track the issue here turbot/steampipe-plugin-sdk#702. Please feel free to reopen the issue if you want to share or discuss anything. |
Describe the bug
when running a new query on aws_route_53_record an interface conversion error is emittied when using an 'in' clause on the
zone_id
fieldError: interface conversion: interface {} is []interface {}, not string (SQLSTATE HV000)
manipulating the
.cache
settings shows the issue, a work around was to change the qualifiers to populate the cache, then the followup query with anin
clause worksSteampipe version (
steampipe -v
)Steampipe v0.21.1
Plugin version (
steampipe plugin list
)0.121.1
To reproduce
Expected behavior
in clause should work from teh first query
The text was updated successfully, but these errors were encountered: