[
https://issues.apache.org/jira/browse/SLING-9766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-9766.
----------------------------------------
Resolution: Invalid
Invalid, sorry for the noise...our own cache only stores queries so it is
correct to omit selectors in the cache key. They will be taken into account by
the HTTP front-end when caching, as they are part of the URL.
> GraphQL query cache key does not take selectors into account
> ------------------------------------------------------------
>
> Key: SLING-9766
> URL: https://issues.apache.org/jira/browse/SLING-9766
> Project: Sling
> Issue Type: Task
> Components: GraphQL
> Affects Versions: GraphQL Core 0.0.6
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Major
>
> I think bHash and cHash should be different here, as the selectors influence
> the query results and as such need to be taken into account:
> {code}
> String selectors = "something"
> String bHash = provider.cacheQuery(queryText, path, null);
> String cHash = provider.cacheQuery(queryText, path, selectors);
> {code}
> I'll submit a pull request.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
