[jira] [Commented] (SLING-9732) Friendly Names / Alias for persisted GraphQL queries

["Bertrand Delacretaz (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-9732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197701#comment-17197701 ] 

Bertrand Delacretaz commented on SLING-9732:
--------------------------------------------

It would be good to know what the use case behind this is.

The current persisted queries implementation makes no guarantees that as to how long they are kept, so if a more durable storage is desired I suppose that's for a different use case than "just" taking advantage of HTTP caches, which is what the current implementation does. 

> Friendly Names / Alias for persisted GraphQL queries
> ----------------------------------------------------
>
>                 Key: SLING-9732
>                 URL: https://issues.apache.org/jira/browse/SLING-9732
>             Project: Sling
>          Issue Type: New Feature
>          Components: GraphQL
>            Reporter: Gilles Knobloch
>            Priority: Major
>
> The current implementation generates a URL with a hash, for instance \{{/persisted/9bae4aa26ea4b2e06889a1e02179e02a902211bf970185c45bceba537107e2fc}}
> It would be great to be able to specify a "friendly name" that an external application could use, for instance {{/persisted/listArticles}}
> Should probably have things like
> * POST - register a query, ensuring a unique name is used
> * PUT - to update existing query
> * DELETE - to remove a persisted query
> I wonder if there should be some namespacing for the query name, like {{/persisted/projectA/listArticles}} and {{/persisted/projectB/listArticles}} to give it more flexibility.
> And probably an endpoint for listing existing queries within such a scope.



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