Added Ranger and Resource group documentation for kill_query
#27055
+8
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis PR fills in missing documentation for the system.runtime.kill_query() procedure by adding guidance in both the Resource Group and Ranger Access Control sections to ensure users properly configure permissions and query type for direct execution of kill_query. Entity relationship diagram for Ranger policy configuration for kill_queryerDiagram
USER ||--o{ POLICY : has
POLICY {
string schema
string database
string procedure
string permission
}
POLICY ||--o{ PROCEDURE : applies_to
PROCEDURE {
string name
}
USER {
string user_id
}
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
mosabua
requested changes
Oct 24, 2025
| `CREATE`, `ALTER`, and `DROP` statements for schemas, tables, views, and | ||
| materialized views, as well as statements that manage prepared statements, | ||
| privileges, sessions, and transactions. | ||
| privileges, sessions, and transactions. Also when external clients need the |
There was a problem hiding this comment.
Suggested change
| privileges, sessions, and transactions. Also when external clients need the | |
| privileges, sessions, and transactions. When external clients need access to the |
| materialized views, as well as statements that manage prepared statements, | ||
| privileges, sessions, and transactions. | ||
| privileges, sessions, and transactions. Also when external clients need the | ||
| `system.runtime.kill_query()` procedure to kill queries, this `queryType` |
There was a problem hiding this comment.
Suggested change
| `system.runtime.kill_query()` procedure to kill queries, this `queryType` | |
| `system.runtime.kill_query()` procedure to stop running queries, this `queryType` |
| privileges, sessions, and transactions. | ||
| privileges, sessions, and transactions. Also when external clients need the | ||
| `system.runtime.kill_query()` procedure to kill queries, this `queryType` | ||
| should be used to make sure the `kill_query()` is executed directly and |
There was a problem hiding this comment.
Suggested change
| should be used to make sure the `kill_query()` is executed directly and | |
| must be used to make sure the `kill_query()` is executed directly and |
| execute any query. | ||
| * To allow this, create a policy in Apache Ranger for a `trinouser` resource | ||
| with value `{USER}` and with the `impersonate` permission for user `{USER}`. | ||
| * External clients might use the `system.runtime.kill_query()` procedure to |
There was a problem hiding this comment.
Suggested change
| * External clients might use the `system.runtime.kill_query()` procedure to | |
| * External clients can use the `system.runtime.kill_query()` procedure to |
| * To allow this, create a policy in Apache Ranger for a `trinouser` resource | ||
| with value `{USER}` and with the `impersonate` permission for user `{USER}`. | ||
| * External clients might use the `system.runtime.kill_query()` procedure to | ||
| kill running queries by id. Add a policy with Schema `system`, Database |
There was a problem hiding this comment.
Suggested change
| kill running queries by id. Add a policy with Schema `system`, Database | |
| kill running queries. Add a policy with Schema `system`, Database |
| privileges, sessions, and transactions. Also when external clients need the | ||
| `system.runtime.kill_query()` procedure to kill queries, this `queryType` | ||
| should be used to make sure the `kill_query()` is executed directly and | ||
| isn't queued to wait for the initial query to finish. |
There was a problem hiding this comment.
Did you verify this behavior with testing it manually?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added some missing documentation about the
system.runtime.kill_query()procedure in Ranger and Resource group sections.Release notes
( X ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:
Summary by Sourcery
Add documentation about the system.runtime.kill_query() procedure in the resource groups guide and the Ranger access control guide
Documentation: