[
https://issues.apache.org/jira/browse/SLING-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366534#comment-17366534
]
Bertrand Delacretaz commented on SLING-10503:
---------------------------------------------
I'm not sure if we even need to log the schema definition, as you mention it
can be large and it can be recreated based on the Resource and selectors.
It that works for you I suggest changing the log patterns to remove the schemas
and include the selectors, I think that will keep the logs reasonably small
while providing all the required information.
And use just the ERROR level. Or should that be INFO? I suspect those errors
are most often due to client errors, would switching to INFO be good from your
point of view?
> DefaultQueyExecutor should not log the full Schema Definition on error
> ----------------------------------------------------------------------
>
> Key: SLING-10503
> URL: https://issues.apache.org/jira/browse/SLING-10503
> Project: Sling
> Issue Type: Improvement
> Components: GraphQL
> Affects Versions: GraphQL Core 0.0.10
> Reporter: Denis Moret
> Priority: Major
>
> If an exception is caught during a query execution, the full schema
> definition is logged. If the schema is large or if the error is repeating, it
> might induce a large quantity of logs.
> I would suggest to log the schema definition on DEBUG log level only.
> [https://github.com/apache/sling-org-apache-sling-graphql-core/blob/5d43e133d6c0d29feb7499e28cb9a3f617b5a8a4/src/main/java/org/apache/sling/graphql/core/engine/DefaultQueryExecutor.java#L231]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
