[
https://issues.apache.org/jira/browse/ASTERIXDB-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671952#comment-16671952
]
ASF subversion and git services commented on ASTERIXDB-2286:
------------------------------------------------------------
Commit 654474692dd19dd42e0b9efcc8209d05a8c41b2e in asterixdb's branch
refs/heads/master from [~alsuliman]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=6544746 ]
[ASTERIXDB-2286][COMP] Parallel sort changes p.2
- user model changes: no
- storage format changes: no
- interface changes: no
details:
This patch is change the way the SequentialMergeExchangePOperator
connector computes its local property instead of blindly
propagating the child's local property.
The patch also includes minor code clean-ups (moved some methods down)
Change-Id: Ie37e03b6fc6e55fc21f8324c0f09a7fa05b51769
Reviewed-on: https://asterix-gerrit.ics.uci.edu/3005
Integration-Tests: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Contrib: Jenkins <[email protected]>
Reviewed-by: Dmitry Lychagin <[email protected]>
> Parallel Sort Optimization
> --------------------------
>
> Key: ASTERIXDB-2286
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2286
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: COMP - Compiler, FUN - Functions, HYR - Hyracks
> Reporter: Ali Alsuliman
> Assignee: Ali Alsuliman
> Priority: Major
> Labels: triaged
>
> The current plan for queries with ORDER BY clauses consists of two phases;
> sorting the data locally in each partition and then sort-merging the data in
> one single partition. Even though the local sort happens in parallel, this
> effort is wasted by the fact that the merge is happening at one partition. It
> is desired to remove the merge step and do a true parallel sort where data is
> range-partitioned across the cluster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
