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
{{ message }}
This repository has been archived by the owner on Nov 8, 2021. It is now read-only.
In the context of the customer Yuka we encountered an issue where (according to Nikola)
GraphQL never responds to the query and most likely the 502s they are reporting are a result of some gateway timeout
To remedy this it was necessary for us to clear the ROS-level Realm cache, which is cumbersome and requires as well the customer to issue a service request.
Can we please add a convenience api to allow either Realm SE's or even the customer to remedy this without involving engineering. Proposed is a schema as follows:
DELETE /graphql/schema/:path
In the context of the customer Yuka we encountered an issue where (according to Nikola)
To remedy this it was necessary for us to clear the ROS-level Realm cache, which is cumbersome and requires as well the customer to issue a service request.
Can we please add a convenience api to allow either Realm SE's or even the customer to remedy this without involving engineering. Proposed is a schema as follows:
DELETE /graphql/schema/:path
We can then update the documentation here to reflect this:
https://github.com/realm/realm-graphql-service#endpoints
The text was updated successfully, but these errors were encountered: