Michael Penick
Michael Penick
There's a specific user that's waiting for this feature. I'd like to have them try this out before merging.
This can be merged after a review.
This also fixes issues with incorrect element indexes being used in errors.
Added a fairly well tested PR for this https://github.com/graphql-go/graphql/pull/536.
Yeah, this is almost definitely a prepared statement caching issue. Maybe we can invalidate by store and invalidate by keyspace/table?
Maybe this should supersede single keyspace mode?
> I think that in DSE system_schema tables use row-based access control (RLAC). If the user has access to 1 ks, the following queries will return the correct values: Oh...
The graphql-playground can fail because of CORs (https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors). After https://github.com/datastax/cassandra-data-apis/pull/119 is merged you can use the following configuration to access from any IP address. `docker run -e "DATA_API_ACCESS_CONTROL_ALLOW_ORIGIN=*"`
Good catch.
It sounds like you might want to implement a custom `AuthenticationService` (authn) and `AuthorizationService` (authz). The token-based auth. service is very simple and can be used as a skeleton for...