[
https://issues.apache.org/jira/browse/GEODE-8675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224942#comment-17224942
]
ASF subversion and git services commented on GEODE-8675:
--------------------------------------------------------
Commit 7f19d9cb19efeedf0135a310a6e804ea76254942 in geode's branch
refs/heads/develop from Donal Evans
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7f19d9c ]
GEODE-8675: Log at query start when <trace> is enabled (#5690)
* GEODE-8675: Log at query start when <trace> is enabled
- Log the query string when query trace begins
- Replace uses of cache.getLogger() with LogService.getLogger() in DefaultQuery
- Update docs to reflect new logging
Authored-by: Donal Evans <doev...@vmware.com>
> When <TRACE> is enabled in a query, log at the start of the query as well as
> the end
> ------------------------------------------------------------------------------------
>
> Key: GEODE-8675
> URL: https://issues.apache.org/jira/browse/GEODE-8675
> Project: Geode
> Issue Type: Improvement
> Components: docs, querying
> Reporter: Donal Evans
> Assignee: Donal Evans
> Priority: Major
> Labels: pull-request-available
>
> Currently, if queries are run with {{{{<TRACE>}}}} prepended to the query,
> the query string, its duration, the number of results, and any indexes used
> are logged at {{info}} level once the query finishes, to aid in query
> debugging. It would be useful to also log the query string when the query
> begins, to help in cases where the query either does not complete, or takes
> an extremely long time to complete.
> Documentation, specifically the Query Debugging page, will also need to be
> updated to describe this new behaviour.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
