[
https://issues.apache.org/jira/browse/SLING-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lenard Palko updated SLING-12221:
---------------------------------
Description:
The version of graphql-java currently used is 20.1, but version 20.3 offers the
possibility to configure also MAX_QUERY_CHARACTERS, in addition to
MAX_QUERY_TOKENS and MAX_WHITESPACE_TOKENS.
[https://github.com/graphql-java/graphql-java/blob/v20.3/src/main/java/graphql/parser/ParserOptions.java#L24]
This would allow to configure the full query length in case the already
existing configurations limits are hit.
was:The version of graphql-java currently used is 20.1, but AEM runtime
already uses version 20.3 so we could upgrade the version used in
sling.graphql.core as well to the same version.
> Upgrade grahpql-java version to 20.3
> ------------------------------------
>
> Key: SLING-12221
> URL: https://issues.apache.org/jira/browse/SLING-12221
> Project: Sling
> Issue Type: Bug
> Components: GraphQL
> Affects Versions: GraphQL Core 0.0.26
> Reporter: Lenard Palko
> Priority: Minor
>
> The version of graphql-java currently used is 20.1, but version 20.3 offers
> the possibility to configure also MAX_QUERY_CHARACTERS, in addition to
> MAX_QUERY_TOKENS and MAX_WHITESPACE_TOKENS.
> [https://github.com/graphql-java/graphql-java/blob/v20.3/src/main/java/graphql/parser/ParserOptions.java#L24]
> This would allow to configure the full query length in case the already
> existing configurations limits are hit.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
