You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@s2graph.apache.org by "Daewon Jeong (JIRA)" <ji...@apache.org> on 2018/03/29 05:21:00 UTC
[jira] [Assigned] (S2GRAPH-191) Providing request / response
logging to GraphQL server and removing println
[ https://issues.apache.org/jira/browse/S2GRAPH-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daewon Jeong reassigned S2GRAPH-191:
------------------------------------
Assignee: Daewon Jeong
> Providing request / response logging to GraphQL server and removing println
> ----------------------------------------------------------------------------
>
> Key: S2GRAPH-191
> URL: https://issues.apache.org/jira/browse/S2GRAPH-191
> Project: S2Graph
> Issue Type: Improvement
> Reporter: Daewon Jeong
> Assignee: Daewon Jeong
> Priority: Minor
> Labels: usability
>
> The GraphQL server, which is still the experiment phase, does not provide logging, but prints the contents of the server to stdout using the println method.
> Therefore, there is a problem that the contents of the error are not properly reported at the time of development, which makes debugging impossible.
> Improve the above problem
> The logger uses the slf4j interface in accordance with the outline of the existing -S2GRAPH-117(-Cleaner logging library usage)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)