GitHub user hbdeshmukh opened a pull request:

    https://github.com/apache/incubator-quickstep/pull/10

    Reorder query id parameter in various work order and operator constructors

    This is a follow up of the review comments in PR #8. The query ID parameter 
used in various constructors of relational operators and work orders is the 
first parameter.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/incubator-quickstep 
reorder-query-id-param

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-quickstep/pull/10.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 #10
    
----
commit 15a2114a2c64c05f8a1b23831496fcf606a38d5d
Author: Harshad Deshmukh <[email protected]>
Date:   2016-06-08T14:14:20Z

    Reordered query ID in aggregation operator

commit d67f61e1651cb68243d78728cc1ce6c68bb08fb1
Author: Harshad Deshmukh <[email protected]>
Date:   2016-06-08T14:36:18Z

    Reordered query ID in operators and work orders.
    
    Reordered query ID in CreateIndex.
    
    Reordered query ID in delete.
    
    Reordered query ID in destroy hash.
    
    Reordered query ID in Drop table.
    
    Reordered query ID in Finalize aggregate
    
    Reordered query ID in hash join
    
    Reordered query ID in insert op
    
    Reordered query ID in nested loops
    
    Reordered query ID in rebuild
    
    Reordered query ID in sample
    
    Reordered query ID in save blocks
    
    Reordered query ID in select
    
    Reordered query ID in sort merge
    
    Reordered query ID in sort run
    
    Reordered query ID in table gen
    
    Reorder query ID in text scan
    
    Reordered query ID in update

----


---
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.
---

Reply via email to