You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Oleg Valuyskiy (Jira)" <ji...@apache.org> on 2025/10/03 11:06:00 UTC

[jira] [Created] (IGNITE-26597) Fix SqlFieldsQuery.setQueryInitiatorId propagation for thin client in SQL_QUERIES system view

Oleg Valuyskiy created IGNITE-26597:
---------------------------------------

             Summary: Fix SqlFieldsQuery.setQueryInitiatorId propagation for thin client in SQL_QUERIES system view
                 Key: IGNITE-26597
                 URL: https://issues.apache.org/jira/browse/IGNITE-26597
             Project: Ignite
          Issue Type: Bug
            Reporter: Oleg Valuyskiy
            Assignee: Oleg Valuyskiy


The {{SqlFieldsQuery}} API allows attaching custom user-defined information via the {{setQueryInitiatorId}} method. This value is expected to appear in the corresponding field of the {{SQL_QUERIES}} system view, enabling tracking of query originators.

Currently, this behavior works correctly when a query is created through a *server node* or a {*}thick client{*}: the {{queryInitiatorId}} set in {{SqlFieldsQuery}} is properly propagated and displayed in {{{}SQL_QUERIES{}}}.

However, when a query is executed via a {*}thin client{*}, the {{queryInitiatorId}} is ignored. In this case, the system view shows the default value for the field, as if {{setQueryInitiatorId}} had not been invoked.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)