GitHub user jihoonson opened a pull request:
https://github.com/apache/tajo/pull/969
TAJO-2082: Aggregation on a derived table which includes union can cause
incorrect result
I didn't add unit test because it is difficult to reproduce this bug with
unit test.
IMO, it is better to add a verifier to test global plan. I created a jira
ticket for global plan verifier.
(https://issues.apache.org/jira/browse/TAJO-2084)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jihoonson/tajo-2 TAJO-2082
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/969.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #969
----
commit b47ba9a9016c1bb7f763157c61915491af58c12f
Author: Jihoon Son <[email protected]>
Date: 2016-02-25T08:06:18Z
Add shuffle info to master plan
commit db17a92b91fc648dbd5523cfc2b08df19958f448
Author: Jihoon Son <[email protected]>
Date: 2016-02-25T15:19:55Z
Add PlanContext.
commit 00943976a1ba6172082f9b1f10e2875aec440145
Author: Jihoon Son <[email protected]>
Date: 2016-02-26T09:26:42Z
TAJO-2082
commit c1af7a88663d551d99da4081e8b02e7b99914861
Author: Jihoon Son <[email protected]>
Date: 2016-02-29T07:37:50Z
Refactoring stage
commit 3ee7bbbc464eaacd92b4c86fde62c9adb98ff32a
Author: Jihoon Son <[email protected]>
Date: 2016-03-01T05:32:48Z
Test finished.
commit 5ac73773f867bf234ec86c49adc116b99792b695
Author: Jihoon Son <[email protected]>
Date: 2016-03-01T05:40:47Z
fix comment
----
---
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.
---
