tree b1a886d466d92f091bec971eb22a3e9e8f72fcd2
parent 76e54891e7925d26c97eaeab09ca9a3368836ce8
author QiangCai <qiangcai@qq.com> 1590940907 +0800
committer Jacky Li <jacky.likun@qq.com> 1590978392 +0800

[CARBONDATA-3837] Fallback to the original plan when mv rewrite throw exception

Why is this PR needed?
All plans are checking MVRewriteRule,
if MVRewriteRule throw an exception, it will lead to query failure

What changes were proposed in this PR?
Only the query should check MVRewriteRule, other plans should skip it quickly.

catch all exceptions of MVRewriteRule, and fallback to original plan.

Does this PR introduce any user interface change?

No
Is any new testcase added?

Yes

This closes #3777