Skip to content

Port ArrayRemove, ArrayRemoveN, ArrayRemoveAll to functions-array subcrate#9656

Merged
jayzhan211 merged 2 commits into
apache:mainfrom
erenavsarogullari:Issue-9635
Mar 18, 2024
Merged

Port ArrayRemove, ArrayRemoveN, ArrayRemoveAll to functions-array subcrate#9656
jayzhan211 merged 2 commits into
apache:mainfrom
erenavsarogullari:Issue-9635

Conversation

@erenavsarogullari

@erenavsarogullari erenavsarogullari commented Mar 17, 2024

Copy link
Copy Markdown
Member

Which issue does this PR close?

Closes #9635.

What changes are included in this PR?

This PR aims to do following changes in terms of Epic #9285:
ArrayRemove, ArrayRemoveN, ArrayRemoveAll are ported to functions-array subcrate.

Are these changes tested?

Yes, all array.slt and unnest.slt based ArrayRemove, ArrayRemoveN, ArrayRemoveAll tests are passed.

Are there any user-facing changes?

No

@github-actions github-actions Bot added logical-expr Logical plan and expressions physical-expr Changes to the physical-expr crates labels Mar 17, 2024
@erenavsarogullari

erenavsarogullari commented Mar 18, 2024

Copy link
Copy Markdown
Member Author

Current Rust / cargo test (win64) build stage failure seems to be related environmental. We can re-trigger this stage if possible.

D:\a\_temp\45213694-13e6-4eb8-97ae-555da09c8695.sh: line 2: /c/Users/runneradmin/.cargo/bin/rustup: Device or resource busy
Error: Process completed with exit code 126.

array_except(
make_array(vec![lit(1), lit(2), lit(3)]),
make_array(vec![lit(1), lit(2)]),
),

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.

I think you accidentally remove it. Also, add remove's too

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Thanks for the review, addressed.

@jayzhan211

Copy link
Copy Markdown
Contributor

Current Rust / cargo test (win64) build stage failure seems to be related environmental. We can re-trigger this stage if possible.

D:\a\_temp\45213694-13e6-4eb8-97ae-555da09c8695.sh: line 2: /c/Users/runneradmin/.cargo/bin/rustup: Device or resource busy
Error: Process completed with exit code 126.

It seems like an issue from github

rust-lang/rustup#3709

/// [[1, 2, 3], [2, 3, 4], [2, 3, 4]], [[1, 2, 3], [2, 3, 4], [3, 4, 5]], 1, false => [true, false, false]
/// )
/// ```
pub(crate) fn compare_element_to_list(

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.

There are three duplicated code including this one, can you remove other two?

@jayzhan211 jayzhan211 left a comment

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.

LGTM

@jayzhan211

jayzhan211 commented Mar 18, 2024

Copy link
Copy Markdown
Contributor

@erenavsarogullari Let me merge this first, those duplications can be removed later

@jayzhan211 jayzhan211 merged commit c7a72e6 into apache:main Mar 18, 2024
@erenavsarogullari

Copy link
Copy Markdown
Member Author

@jayzhan211 Thanks for the merge. I will address duplication by separate PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

logical-expr Logical plan and expressions physical-expr Changes to the physical-expr crates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Port ArrayRemove, ArrayRemoveN, ArrayRemoveAll to functions-array subcrate

2 participants