-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Unable to filter remote schema with "where" #8901
Comments
Thanks for bringing the issue to our attention. This issue looks similar to this reported earlier by another user of our community. You may track the issue till its resolution. Meanwhile, there is a workaround for this, as suggested in the other ticket: Please let us know if the info suffice. |
Thanks @adas98012 That does sound similar. I'll wait for the bug to be fixed. |
We don't have an ETA, but this in radar of the engineering team. We'll update the status of the issue accordingly. Thanks for your patience. |
@munjalpatel - we have fixed the issue in v2.13, can you please check and update? |
…e files (#8901) GitOrigin-RevId: c97f36ffc68ac075354a0da8b2caf19ddc26e20c
Version Information
Server Version: 2.10.1
Environment
OSS
What is the current behaviour?
When I execute the above query in Hasura Console UI (as an admin), it works just fine.
However, I get the following error when running it as a particular user role.
Here are the remote schema permissions given to the role
Even though, I am properly giving
input subscriptions_bool_exp
permission to the role.Am I missing any other permission?
What is the expected behaviour?
The query should continue to work fine given permissions are correct.
The text was updated successfully, but these errors were encountered: