Skip to content

Repo sync for protected branch #2863

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
learn-build-service-prod merged 4 commits into from
Mar 17, 2026
+3 −0
Merged

Repo sync for protected branch #2863

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
abe9ef5
cache-policy: Added an example for specifying the data scope when usi…
zivcaspi Mar 17, 2026
6ef70dd
Merge pull request #7417 from zivcaspi/users/zivc/cache-policy
prmerger-automator[bot] Mar 17, 2026
0fdd42c
Merge pull request #7419 from MicrosoftDocs/main
learn-build-service-prod[bot] Mar 17, 2026
6282682
Merging changes synced from https://github.com/MicrosoftDocs/dataexpl…
Mar 17, 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
3 changes: 3 additions & 0 deletions data-explorer/kusto/management/cache-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,9 @@ There are several query possibilities:
Possible values are the same as for the client request property.
* Add a `datascope=...` text immediately after a table reference in the query body.
Possible values are `all` and `hotcache`.
If the table is referenced by using the [table() function](../query/table-function.md ),
then the data scope is provided as a second string argument to the function.
For example, `table("T", "hotcache") | count` means the same as `T datascope=hotcache | count`.

The `default` value indicates use of the default settings, which determine that the query should cover all data.

Expand Down