You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the bug? index tag set to the EMRS job run does not include datasource name and schema when those are not explicitly specified in the query.
Example query: CREATE MATERIALIZED VIEW mv1 AS ....
In this case, index tag should be flint_{datasourceName}_{schema}_mv1, but it is set to flint_mv1
How can one reproduce the bug?
Steps to reproduce the behavior:
start async-query with CREATE MATERIALIZED VIEW mv1 AS SELECT ...
check EMR job run
What is the expected behavior? index tag should look like flint_{datasourceName}_{schema}_mv1
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.
The text was updated successfully, but these errors were encountered:
Flint grammar allows this because we can infer the current catalog and database in Spark. Probably we should consider validating and disallowing this in SQL plugin.
Flint grammar allows this because we can infer the current catalog and database in Spark. Probably we should consider validating and disallowing this in SQL plugin.
+1, since Plugin doesn't have the catalog info exposure
What is the bug?
index
tag set to the EMRS job run does not include datasource name and schema when those are not explicitly specified in the query.Example query:
CREATE MATERIALIZED VIEW mv1 AS ....
In this case,
index
tag should beflint_{datasourceName}_{schema}_mv1
, but it is set toflint_mv1
How can one reproduce the bug?
Steps to reproduce the behavior:
CREATE MATERIALIZED VIEW mv1 AS SELECT ...
What is the expected behavior?
index
tag should look likeflint_{datasourceName}_{schema}_mv1
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.
The text was updated successfully, but these errors were encountered: