# Workload Dremio EE feature

**URL:** <https://community.dremio.com/t/workload-dremio-ee-feature/12273>\
**Category:** Uncategorized\
**Created:** [September 9, 2024, 7:35am UTC](https://community.dremio.com/t/workload-dremio-ee-feature/12273 "2024-09-09T07:35:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Arnie](https://avatars.discourse-cdn.com/v4/letter/a/ba9def/32.png) [@Arnie](https://community.dremio.com/u/Arnie)\
**Post date:** [September 9, 2024, 7:35am UTC](https://community.dremio.com/t/workload-dremio-ee-feature/12273/1 "2024-09-09T07:35:16Z")

</div>

Hello  
I wonder if anybody could tune workload feature to set queue depending on sourcename ? I mean when dremio engine calculates costs it knows which sourcename is involved so why would not it use the information to set job in proper queue ?  
Also is there any tweak to route ‘stupid jobs’ is dedicated queue or just reject it. Logically Dremio Admin would be able to define what are stupid jobs.

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [September 14, 2024, 1:31am UTC](https://community.dremio.com/t/workload-dremio-ee-feature/12273/2 "2024-09-14T01:31:20Z")

</div>

@Arnie

Current rules available are [Workload Management | Dremio Documentation](https://docs.dremio.com/current/admin/workloads/workload-management#rule-examples)

Are you not able to route using any of them like those long running jobs coming from a certain user or cost etc?

---

<div class="post-metadata">

**Author:** ![Arnie](https://avatars.discourse-cdn.com/v4/letter/a/ba9def/32.png) [@Arnie](https://community.dremio.com/u/Arnie)\
**Post date:** [September 16, 2024, 11:49am UTC](https://community.dremio.com/t/workload-dremio-ee-feature/12273/3 "2024-09-16T11:49:49Z")

</div>

Hello  
To route based on user name or group membership is done but it’s not enough. Cost is not predictible from an admin point of view and can only be seen via le logs.  
My will and idea is to route based on source database name.  
Why ?  
because some sources can be queried with no restrictions and limits, while some other sources should be queried carefully.

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [September 16, 2024, 2:17pm UTC](https://community.dremio.com/t/workload-dremio-ee-feature/12273/4 "2024-09-16T14:17:39Z")

</div>

@Arnie I will check if that feature request exists,

When queries come from a certain source via JDBC (if not machine generated), a `ROUTING_TAG` or a `ROUTING_QUEUE` can be added and that sent to a separate engine

---

<div class="post-metadata">

**Author:** ![Arnie](https://avatars.discourse-cdn.com/v4/letter/a/ba9def/32.png) [@Arnie](https://community.dremio.com/u/Arnie)\
**Post date:** [September 16, 2024, 4:22pm UTC](https://community.dremio.com/t/workload-dremio-ee-feature/12273/5 "2024-09-16T16:22:24Z")

</div>

According to me, Routing\_tag or Routing\_queue are parameters on the dremio client side (analytics tools) …  
Also consider those clients use Arrow\_Flight protocol.

My concern it to use a setting based on ‘SOURCE\_NAME’ … is the query uses one of the source that, the query should be routed in a queue

(  
USER IN (‘JRyan’, ‘PDirk’, ‘CPhillips’)  
OR is\_member(‘superadmins’)  
)  
AND query\_type IN (‘ODBC’)  
AND EXTRACT(HOUR FROM CURRENT\_TIME)  
BETWEEN 9 AND 18  
AND SOURCE\_NAME IN (‘hr\_db’,‘account\_db’)