Skip to content
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

Fix example reference in resource groups doc #6568

Merged
merged 1 commit into from
Jan 14, 2021
Merged

Fix example reference in resource groups doc #6568

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
12 changes: 6 additions & 6 deletions docs/src/main/sphinx/admin/resource-groups.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,12 +141,12 @@ There are four selectors, that define which queries run in which resource group:
dynamically-created per-user pipeline group under the ``global.pipeline`` group.

* The fifth selector matches queries that come from BI tools which have a source matching the regular
expression ``jdbc#(?<toolname>.*)``, and have client provided tags that are a superset of ``hi-pri``.
These are placed in a dynamically-created sub-group under the ``global.pipeline.tools`` group. The dynamic
sub-group are created based on the named variable ``toolname``, which is extracted from the in the
regular expression for source. Consider a query with a source ``jdbc#powerfulbi``, user ``kayla``, and
client tags ``hipri`` and ``fast``. This query is routed to the ``global.pipeline.bi-powerfulbi.kayla``
resource group.
expression ``jdbc#(?<toolname>.*)`` and have client provided tags that are a superset of ``hipri``.
These are placed in a dynamically-created sub-group under the ``global.adhoc`` group.
The dynamic sub-groups are created based on the values of named variables ``toolname`` and ``user``.
The values are derived from the source regular expression and the query user respectively.
Consider a query with a source ``jdbc#powerfulbi``, user ``kayla``, and client tags ``hipri`` and ``fast``.
This query is routed to the ``global.adhoc.bi-powerfulbi.kayla`` resource group.

* The last selector is a catch-all, which places all queries that have not yet been matched into a per-user
adhoc group.
Expand Down