GitHub user sirpkt opened a pull request:
https://github.com/apache/tajo/pull/364
TAJO-1283: ORDER BY with the first descending order causes wrong results
As BaseTupleComparator already handles both ascending and descending sort
keys, remove unnecessary DescendingTupleRangeComparator class.
- We do not need to consider whether the first sort key is ascending or
descending in scheduleRangeShuffledFetches() so related codes are removed.
- Add TEST_MIN_TASK_NUM support in getNonLeafTaskNum() of Stage.java for
Test purpose.
'mvn clean install' passed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sirpkt/tajo TAJO-1283
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/364.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 #364
----
commit 30a16e3f166ca34c9391a4dbad64bd2a92b58737
Author: Keuntae Park <[email protected]>
Date: 2015-01-28T06:37:07Z
As BaseTupleComparator already handles both ascending and descending sort
keys, remove unnecessary DescendingTupleRangeComparator class.
- We do not need to consider whether the first sort key is ascending or
descending in scheduleRangeShuffledFetches().
- Add TEST_MIN_TASK_NUM support in getNonLeafTaskNum() of Stage.java for
Test purpose.
commit 61619daa98b3d7e89f902e6f587047af54a0a2de
Author: Keuntae Park <[email protected]>
Date: 2015-01-28T06:41:39Z
Merge branch 'master' into TAJO-1283
----
---
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.
---
