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
Is your feature request related to a problem? Please describe.
Currently, introspection queries and their response data is saved to the cache, which also populated in Redis.
If I have an extremely large schema and I have clients making slightly different introspection queries this can start sending lots of data to my Redis instance and eating up performance, bandwith, and storage
Describe the solution you'd like
Allow configuring or disabling if introspection responses are cached or not
supergraph:
introspection:
enabled: truecache: false # Not sure what is better here. I think default should be cache on, so how do we turn it off?cache:
in_memory:
enabled: falseredis:
enabled: false
Describe alternatives you've considered
There is no control over this today. I need to enforce that introspection is all the same or I can disable it entirely
supergraph:
introspection: false
Additional context
Maybe as part of the issue #4608 we can add more features
OR
We could lock down introspection to only 1 predefined operation: #4871
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, introspection queries and their response data is saved to the cache, which also populated in Redis.
router/apollo-router/src/introspection.rs
Line 79 in 615b74d
If I have an extremely large schema and I have clients making slightly different introspection queries this can start sending lots of data to my Redis instance and eating up performance, bandwith, and storage
Describe the solution you'd like
Allow configuring or disabling if introspection responses are cached or not
Enabled cache
Disabled cache
Describe alternatives you've considered
There is no control over this today. I need to enforce that introspection is all the same or I can disable it entirely
Additional context
Maybe as part of the issue #4608 we can add more features
OR
We could lock down introspection to only 1 predefined operation: #4871
The text was updated successfully, but these errors were encountered: