Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/379#issuecomment-74479771
+1
The patch contains a workaround code which can fix the bug right now.
I have some comments. Your workaround code seems to try to firstly find the
order of joins whose join types is same. In my opinion, this approach may miss
some of join order combinations. It may cause sub-optimal join orders in some
cases. I think that the right way is to improve the findBestPair() to find only
associative join orders. It would be great if we do it in another jira.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
