GitHub user jihoonson opened a pull request:

    https://github.com/apache/tajo/pull/592

    TAJO-1630: Test failure after TAJO-1130

    I've changed only two lines as follows. Everything else is related to unit 
tests.
    ```
    diff --git 
a/tajo-core/src/main/java/org/apache/tajo/engine/planner/global/MasterPlan.java 
b/tajo-core/src/main/java/org/apache/tajo/engine/planner/global/MasterPlan.java
    index 22c3751..f8cd1e9 100644
    --- 
a/tajo-core/src/main/java/org/apache/tajo/engine/planner/global/MasterPlan.java
    +++ 
b/tajo-core/src/main/java/org/apache/tajo/engine/planner/global/MasterPlan.java
    @@ -237,13 +237,13 @@ public class MasterPlan {
         sb.append("Order of Execution\n");
         
sb.append("-------------------------------------------------------------------------------");
         int order = 1;
    -    for (ExecutionBlock currentEB : cursor) {
    +    for (ExecutionBlock currentEB : executionOrderCursor) {
           sb.append("\n").append(order).append(": ").append(currentEB.getId());
           order++;
         }
         
sb.append("\n-------------------------------------------------------------------------------\n");
     
    -    for (ExecutionBlock block : cursor) {
    +    for (ExecutionBlock block : executionOrderCursor) {
     
           boolean terminal = false;
    ```

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

    $ git pull https://github.com/jihoonson/tajo-2 TAJO-1630

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

    https://github.com/apache/tajo/pull/592.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 #592
    
----
commit dc93e22c6e31668f7dceed90d9b294d757264808
Author: Jihoon Son <[email protected]>
Date:   2015-05-28T08:06:50Z

    TAJO-1630

----


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