Skip to content

Clarify request_user property description #2895

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
v-regandowner merged 2 commits into from
May 20, 2026
Merged

Clarify request_user property description #2895

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c6fc3c1
Clarify `request_user` property description
yihezkel May 20, 2026
4634221
Update request_user description in request-properties.md
yihezkel May 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion data-explorer/kusto/api/rest/request-properties.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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](../../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). |
Expand Down