From f55c011738b62c93455437282c985640c01bb531 Mon Sep 17 00:00:00 2001 From: rongr Date: Tue, 13 Sep 2022 15:10:16 +0000 Subject: [PATCH] GitBook: [#1429] No subject --- .../advanced/v2-multi-stage-query-engine.md | 34 ++++++++++++++++++- 1 file changed, 33 insertions(+), 1 deletion(-) diff --git a/developers/advanced/v2-multi-stage-query-engine.md b/developers/advanced/v2-multi-stage-query-engine.md index 7980b2ae..46a71c84 100644 --- a/developers/advanced/v2-multi-stage-query-engine.md +++ b/developers/advanced/v2-multi-stage-query-engine.md @@ -32,7 +32,39 @@ To enable the V2 engine, -## Design Details +## Troubleshoot + +The V2 query engine is still in the beta phase, there might be various performance or feature gaps from the current query engine. + +Here are the general troubleshooting steps: + +### Semantic / Runtime errors + +* Try downloading the latest docker image or building from the latest master commit + * We continuously pushes bug fixes for the V2 engine so bugs you encountered might have already been fixed in the latest master build +* Try rewriting your query + * Some of the functions previously supported in the V1 engine might have a new way to express in the new engine. Please check and see if you are using any non-standard SQL functions or semantics. + +### Timeout errors + +* Try reducing the size of the table(s) used: + * Adding higher selectivity filters to the tables +* Try executing part of the subquery or a simplified version of the query first. + * This helps to determine the selectivity and scale of the query being executed. +* Try adding more servers + * The new V2 engine runs distributedly across the entire cluster, adding more servers to partitioned queries such as GROUP BY aggregates, equality JOINs help speed up the query runtime. + +### How to share feedbacks + +please report any bugs in Apache Pinot Slack [V2 engine feedback channel](https://apache-pinot.slack.com/archives/C03Q4A11GC9). Please include: + +* the table/schema config(s) +* the cluster config (zookeeper config, and each components config and scale) +* the problematic SQL query string and corresponding ERROR messages. + + + +## Reference: Design Docs The overall PEP design doc and discussion can be found in the following links