[
https://issues.apache.org/jira/browse/IMPALA-7578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16617727#comment-16617727
]
Tim Armstrong commented on IMPALA-7578:
---------------------------------------
This makes sense to me. I've been meaning to revisit how this all works.
> More flexible placement rules
> -----------------------------
>
> Key: IMPALA-7578
> URL: https://issues.apache.org/jira/browse/IMPALA-7578
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 3.0
> Reporter: Balazs Jeszenszky
> Priority: Major
> Labels: admission-control, resource-management
>
> Currently, placement rules can be defined based on user names or
> (primary/secondary) group names as a direct mapping. This promotes creating
> much more pools than might be needed, and leads to administrative overhead
> when changing names or adding a new user/group.
> It would be good to have a more elaborate mapping, e.g. translate user/group
> names into pools (including potentially mapping multiple users/groups to the
> same pool), either manually or via regular expressions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
