You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2020/10/09 10:22:00 UTC

[jira] [Closed] (SLING-9753) Return a 500 status code if the persisted query cannot be stored in the cache

     [ https://issues.apache.org/jira/browse/SLING-9753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radu Cotescu closed SLING-9753.
-------------------------------

> Return a 500 status code if the persisted query cannot be stored in the cache
> -----------------------------------------------------------------------------
>
>                 Key: SLING-9753
>                 URL: https://issues.apache.org/jira/browse/SLING-9753
>             Project: Sling
>          Issue Type: Bug
>          Components: GraphQL
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: GraphQL Core 0.0.6
>
>
> SLING-9655 added support for GraphQL persisted queries. However, the current implementation still returns a query's cache and allows a client to perform cache retrievals even if the query was not actually stored in the cache.
> This happens due to the LRU cache implemented by {{org.apache.sling.graphql.core.cache.SimpleGraphQLCacheProvider}}, which evicts the oldest entry without checking if the new entry can actually be stored when using a cache memory limit configuration.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)