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
Flint successfully creates skipping indexes on SQL views. However, queries involving applicable filtering conditions aren't rewritten by the skipping index rewriter.
The root cause after investigation is: the skipping index query rewrite occurs post view resolution. While Flint's skipping index metadata stores the view as source, the query plan given to the rewriter is based on the source table with the view replaced already.
How can one reproduce the bug?
CREATE VIEW waf_logs_view_clientip
AS SELECT httpRequest.clientIp as clientIp
FROM waf_logs;
CREATE SKIPPING INDEX ON waf_logs_view_clientip (
clientIp VALUE_SET
) WITH (
auto_refresh = true
);
# InMemoryFileIndex present without rewrite
EXPLAIN
SELECT * FROM glue.default.waf_logs_view_clientip
WHERE clientIp = "127.0.0.1"
What is the expected behavior?
Query should be rewritten with FlintSparkSkippingFileIndex.
The text was updated successfully, but these errors were encountered:
What is the bug?
Flint successfully creates skipping indexes on SQL views. However, queries involving applicable filtering conditions aren't rewritten by the skipping index rewriter.
The root cause after investigation is: the skipping index query rewrite occurs post view resolution. While Flint's skipping index metadata stores the view as source, the query plan given to the rewriter is based on the source table with the view replaced already.
How can one reproduce the bug?
What is the expected behavior?
Query should be rewritten with
FlintSparkSkippingFileIndex
.The text was updated successfully, but these errors were encountered: