Error to route when requestAnalyzerConfig is True #487
Comments
|
I removed the QueryCountBasedRouterProvider, but the latest query from dbt is being routed to the adhoc group. The difference is that the latest query is a CREATE TABLE statement. I conducted 5 tests, and in all of them, the latest query was routed to adhoc. I feel that it might just be a coincidence, because when I try to run just a CREATE TABLE, the query is routed to the large routing group. |
|
Sometimes this error appears in the log |
ndrluis
changed the title
|
I discovered that this error only happens when the requestAnalyzerConfig is set to True. Here is an example of the query: CREATE OR REPLACE TABLE "catalog"."database"."example_table"
WITH (
"extra_properties" = MAP(
ARRAY['optimizer.enabled', 'compaction.enabled'],
ARRAY['false', 'false']
))
AS (
WITH cte_example_sheets AS (
SELECT *
FROM "catalog"."database"."example_source"
)
, cte_example AS (
SELECT
CAST(field1 AS VARCHAR) AS alias1
, CAST(field2 AS VARCHAR) AS alias2
, CAST(field3 AS VARCHAR) AS alias3
, CAST(SPLIT_PART(field4, '-', 1) AS VARCHAR) AS alias4
, CAST(SPLIT_PART(field4, '-', 2) AS VARCHAR) AS alias5
, CAST(field5 AS VARCHAR) AS alias6
, CAST(DATE_PARSE(field6, '%Y-%m-%d %H:%i') AS TIMESTAMP(6)) AS alias7
, CAST(DATE_PARSE(field7, '%Y-%m-%d %H:%i') AS TIMESTAMP(6)) AS alias8
, CAST(DATE_PARSE(field8, '%Y-%m-%d %H:%i') AS TIMESTAMP(6)) AS alias9
, CAST(DATE_PARSE(field9, '%Y-%m-%d %H:%i') AS TIMESTAMP(6)) AS alias10
, CAST(field10 AS VARCHAR) AS alias11
, CAST(field11 AS VARCHAR) AS alias12
, CAST(field12 AS VARCHAR) AS alias13
FROM cte_example_sheets
)
SELECT * FROM cte_example
)The problem is that the exact same query runs without error when I use the Trino CLI as the client, but it returns an error every time I use the DBT client. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I activated the
io.trino.gateway.ha.module.QueryCountBasedRouterProviderand have two routing groups, each with one cluster.I also have a rule that directs queries from the "dbt-trino" source to the
largerouting group. However, when I execute multiple queries, some of them are being routed to theadhocrouting group. Is this expected behavior, considering that the QueryCount router might have higher priority than the routing rule, or is this a bug?Routing Rule
Clusters
Routing History
The text was updated successfully, but these errors were encountered: