Skip to content

[Datasets] Fix zip stage to preserve order when executing the other side - #33649

Merged
ericl merged 2 commits into
ray-project:masterfrom
c21:fix-order
Mar 24, 2023
Merged

[Datasets] Fix zip stage to preserve order when executing the other side#33649
ericl merged 2 commits into
ray-project:masterfrom
c21:fix-order

Conversation

@c21

@c21 c21 commented Mar 23, 2023

Copy link
Copy Markdown
Contributor

Why are these changes needed?

Found bug that ZipStage not preserve order when executing the right side. Though previously we have check if plan has zip or sort stage, that only enforces order from left side, but not enforces order from right side.

See the added unit test for a reproduce example. User encounter the issue when enabling streaming execution on their workload.

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

Signed-off-by: Cheng Su <scnju13@gmail.com>
executor: Executor,
plan: ExecutionPlan,
allow_clear_input_blocks: bool,
preserve_order: bool = False,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall we make it required as other params and as upper call funcs?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah we can make it required. sorry what do you mean by "as upper call funcs"?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, the callers of this function, like execute_to_legacy_block_list.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it, updated.

Signed-off-by: Cheng Su <scnju13@gmail.com>
@ericl ericl added the @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. label Mar 23, 2023
@c21 c21 added tests-ok The tagger certifies test failures are unrelated and assumes personal liability. and removed @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. labels Mar 24, 2023
@ericl
ericl merged commit f22fc11 into ray-project:master Mar 24, 2023
@c21
c21 deleted the fix-order branch March 24, 2023 06:46
elliottower pushed a commit to elliottower/ray that referenced this pull request Apr 22, 2023
…ide (ray-project#33649)

Found bug that `ZipStage` not preserve order when executing the right side. Though previously we have check if plan has zip or sort stage, that only enforces order from left side, but not enforces order from right side.

See the added unit test for a reproduce example. User encounter the issue when enabling streaming execution on their workload.

Signed-off-by: elliottower <elliot@elliottower.com>
ProjectsByJackHe pushed a commit to ProjectsByJackHe/ray that referenced this pull request May 4, 2023
…ide (ray-project#33649)

Found bug that `ZipStage` not preserve order when executing the right side. Though previously we have check if plan has zip or sort stage, that only enforces order from left side, but not enforces order from right side.

See the added unit test for a reproduce example. User encounter the issue when enabling streaming execution on their workload.

Signed-off-by: Jack He <jackhe2345@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tests-ok The tagger certifies test failures are unrelated and assumes personal liability.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants