[
https://issues.apache.org/jira/browse/TAJO-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jihoon Son updated TAJO-1577:
-----------------------------
Attachment: fix_plan_preprocessor.patch
Hi [~navis].
While working on TAJO-1352, I found some bugs in ExplainPlanPreprocessorForTest
and have fixed those bugs. However, this issue is also related to bugs, so I'd
like to share my patch.
I hope that this will be helpful.
> Add test cases to verify join plans
> -----------------------------------
>
> Key: TAJO-1577
> URL: https://issues.apache.org/jira/browse/TAJO-1577
> Project: Tajo
> Issue Type: Test
> Components: test
> Reporter: Jihoon Son
> Fix For: 0.11.0
>
> Attachments: fix_plan_preprocessor.patch
>
>
> We are lacking test cases to verify query plans even though they directly
> affect to query processing performance. This is important especially for join
> queries because their plans can be changed while optimizing join order that
> affects to performance significantly. So, we need to verify the optimal join
> plan first.
> There can be some approaches to test query plans. Here are some candidates
> what I consider.
> * Adding a special class that verifies query plans while traversing it.
> * Verifying the result of *EXPLAIN* query.
> I think that the second approach looks good. Here are some reasons.
> * Easy to implement. It's just string match.
> * Easy to verify both logical plan and global plan without adding any special
> classes to traverse query plan.
> * This is the most important reason. With the second approach, we can
> guarantee that our query planner is deterministic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
