[
https://issues.apache.org/jira/browse/IGNITE-29020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18109328#comment-18109328
]
Dmitry Pavlov commented on IGNITE-29020:
----------------------------------------
Merged to master
https://github.com/apache/ignite/commit/aa3dec022f4408a8a51263ac6c0f1612a5fd73ae
[~alex_pl] thank you for review
> [doc] Document SQL query initiator ID usage
> -------------------------------------------
>
> Key: IGNITE-29020
> URL: https://issues.apache.org/jira/browse/IGNITE-29020
> Project: Ignite
> Issue Type: Task
> Components: documentation
> Reporter: Ignite TC Bot
> Assignee: Ignite TC Bot
> Priority: Major
> Labels: ignite-2
> Fix For: 2.18, 2.19
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> IGNITE-27207 added propagation of SqlFieldsQuery query initiator ID from the
> Java thin client to the server, and IGNITE-27313 added the initiator ID to
> server-side SQL diagnostics.
> The system views documentation already lists INITIATOR_ID, and
> RELEASE_NOTES.txt mentions the changes, but the user documentation does not
> show how to set the initiator ID or how to use it to correlate a client SQL
> request with SYS.SQL_QUERIES / SYS.SQL_QUERIES_HISTORY and server logs.
> Please add a practical SQL API example for
> SqlFieldsQuery.setQueryInitiatorId(...) and mention that Java thin client SQL
> requests use the same SqlFieldsQuery mechanism.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
