From c6fc3c1b5355efd06c65632c2c37a870bb10576a Mon Sep 17 00:00:00 2001 From: Yihezkel Schoenbrun Date: Wed, 20 May 2026 12:00:23 +0200 Subject: [PATCH 1/2] Clarify `request_user` property description Updated the description of the `request_user` property to clarify its purpose and usage in service-side diagnostic traces. --- data-explorer/kusto/api/rest/request-properties.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data-explorer/kusto/api/rest/request-properties.md b/data-explorer/kusto/api/rest/request-properties.md index 3372c39d02..e1087eeb26 100644 --- a/data-explorer/kusto/api/rest/request-properties.md +++ b/data-explorer/kusto/api/rest/request-properties.md @@ -77,7 +77,7 @@ The following table overviews the supported request properties. | `request_readonly_hardline` | `bool` | If set to `true`, then the request operates in a strict read-only mode. The request isn't able to write anything, and any noncompliant functionality, such as plugins, are disabled. This option can't be modified as part of a [set statement](../../query/set-statement.md).| | `request_remote_entities_disabled` | `bool` | If set to `true`, prevents the request from accessing remote databases and remote entities. | | `request_sandboxed_execution_disabled` | `bool` | If set to `true`, prevents the request from invoking code in the sandbox. | -| `request_user` | `string` | Specifies the request user to be used in reporting. For example, [.show queries](../../management/show-queries-command.md). This option can't be modified as part of a [set statement](../../query/set-statement.md).| +| `request_user` | `string` | A free-text, caller-supplied identifier of the user on whose behalf the request is being made. It is captured in service-side diagnostic traces for correlation only. It does **not** populate the `User` column of `.show queries` (that column always reflects the authenticated principal), and it is redacted (shown as `******`) wherever client request properties are surfaced — including `.show queries` and the audit log. To pass caller context that should be visible in `.show queries`, or that should be consumed by the request classification policy, use `request_description` instead. This option can't be modified as part of a [set statement](../../query/set-statement.md). For example, [.show queries](../../management/show-queries-command.md).| | `results_error_reporting_placement` | `string` | Determines the placement of errors in the result set. Options are `in_data`, `end_of_table`, and `end_of_dataset`. | | `results_progressive_enabled` | `bool` | If set to `true`, enables the progressive query stream. This option can't be modified as part of a [set statement](../../query/set-statement.md).| | `results_v2_fragment_primary_tables` | `bool` | Causes primary tables to be sent in multiple fragments, each containing a subset of the rows. This option can't be modified as part of a [set statement](../../query/set-statement.md). | From 4634221e42e6d708beec152c2343ab49dc38a446 Mon Sep 17 00:00:00 2001 From: Yihezkel Schoenbrun Date: Wed, 20 May 2026 12:06:35 +0200 Subject: [PATCH 2/2] Update request_user description in request-properties.md --- data-explorer/kusto/api/rest/request-properties.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data-explorer/kusto/api/rest/request-properties.md b/data-explorer/kusto/api/rest/request-properties.md index e1087eeb26..ee96812707 100644 --- a/data-explorer/kusto/api/rest/request-properties.md +++ b/data-explorer/kusto/api/rest/request-properties.md @@ -77,7 +77,7 @@ The following table overviews the supported request properties. | `request_readonly_hardline` | `bool` | If set to `true`, then the request operates in a strict read-only mode. The request isn't able to write anything, and any noncompliant functionality, such as plugins, are disabled. This option can't be modified as part of a [set statement](../../query/set-statement.md).| | `request_remote_entities_disabled` | `bool` | If set to `true`, prevents the request from accessing remote databases and remote entities. | | `request_sandboxed_execution_disabled` | `bool` | If set to `true`, prevents the request from invoking code in the sandbox. | -| `request_user` | `string` | A free-text, caller-supplied identifier of the user on whose behalf the request is being made. It is captured in service-side diagnostic traces for correlation only. It does **not** populate the `User` column of `.show queries` (that column always reflects the authenticated principal), and it is redacted (shown as `******`) wherever client request properties are surfaced — including `.show queries` and the audit log. To pass caller context that should be visible in `.show queries`, or that should be consumed by the request classification policy, use `request_description` instead. This option can't be modified as part of a [set statement](../../query/set-statement.md). For example, [.show queries](../../management/show-queries-command.md).| +| `request_user` | `string` | A free-text, caller-supplied identifier of the user on whose behalf the request is being made. It is captured in service-side diagnostic traces for correlation only. It does **not** populate the `User` column of [.show queries](../../management/show-queries-command.md) (that column always reflects the authenticated principal), and it is redacted (shown as `******`) wherever client request properties are surfaced. To pass caller context that should be visible in `.show queries`, or that should be consumed by the request classification policy, use `request_description` instead. This option can't be modified as part of a [set statement](../../query/set-statement.md).| | `results_error_reporting_placement` | `string` | Determines the placement of errors in the result set. Options are `in_data`, `end_of_table`, and `end_of_dataset`. | | `results_progressive_enabled` | `bool` | If set to `true`, enables the progressive query stream. This option can't be modified as part of a [set statement](../../query/set-statement.md).| | `results_v2_fragment_primary_tables` | `bool` | Causes primary tables to be sent in multiple fragments, each containing a subset of the rows. This option can't be modified as part of a [set statement](../../query/set-statement.md). |