Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add compare_single_row_of_tables #391

Merged
merged 2 commits into from
Dec 3, 2024
Merged

feat: add compare_single_row_of_tables #391

merged 2 commits into from
Dec 3, 2024

Conversation

iajoiner
Copy link
Contributor

@iajoiner iajoiner commented Nov 25, 2024

Please be sure to look over the pull request guidelines here: https://github.com/spaceandtimelabs/sxt-proof-of-sql/blob/main/CONTRIBUTING.md#submit-pr.

Please go through the following checklist

Rationale for this change

We need to add this function in order to perform sort-merge joins.

What changes are included in this PR?

See title.

Are these changes tested?

Yes.

@iajoiner iajoiner force-pushed the feat/row-comp branch 2 times, most recently from 3698a78 to dc6d940 Compare November 26, 2024 04:32
@iajoiner iajoiner marked this pull request as ready for review November 26, 2024 04:32
@iajoiner iajoiner mentioned this pull request Nov 27, 2024
5 tasks
@iajoiner iajoiner enabled auto-merge November 27, 2024 20:54
@iajoiner iajoiner requested a review from tlovell-sxt December 2, 2024 19:12
tlovell-sxt
tlovell-sxt previously approved these changes Dec 3, 2024
crates/proof-of-sql/src/base/database/order_by_util.rs Outdated Show resolved Hide resolved
crates/proof-of-sql/src/base/database/order_by_util.rs Outdated Show resolved Hide resolved
@tlovell-sxt tlovell-sxt disabled auto-merge December 3, 2024 00:05
@iajoiner iajoiner changed the title feat: add compare_indexes_of_tables_by_columns feat: add compare_single_row_of_tables Dec 3, 2024
@iajoiner iajoiner requested a review from tlovell-sxt December 3, 2024 14:41
@iajoiner iajoiner enabled auto-merge December 3, 2024 17:00
@iajoiner iajoiner merged commit ec101bf into main Dec 3, 2024
11 of 19 checks passed
@iajoiner iajoiner deleted the feat/row-comp branch December 3, 2024 17:28
Copy link

github-actions bot commented Dec 3, 2024

🎉 This PR is included in version 0.52.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

iajoiner added a commit that referenced this pull request Dec 18, 2024
Please be sure to look over the pull request guidelines here:
https://github.com/spaceandtimelabs/sxt-proof-of-sql/blob/main/CONTRIBUTING.md#submit-pr.

# Please go through the following checklist
- [x] The PR title and commit messages adhere to guidelines here:
https://github.com/spaceandtimelabs/sxt-proof-of-sql/blob/main/CONTRIBUTING.md.
In particular `!` is used if and only if at least one breaking change
has been introduced.
- [x] I have run the ci check script with `source
scripts/run_ci_checks.sh`.
- The following upstream PRs have been approved and merged:
  - [x] #391 
  - [x] #396


# Rationale for this change
This PR adds the actual sort-merge join process which completes a part
of #394.
<!--
Why are you proposing this change? If this is already explained clearly
in the linked issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.

 Example:
 Add `NestedLoopJoinExec`.
 Closes #345.

Since we added `HashJoinExec` in #323 it has been possible to do
provable inner joins. However performance is not satisfactory in some
cases. Hence we need to fix the problem by implement
`NestedLoopJoinExec` and speed up the code
 for `HashJoinExec`.
-->

# What changes are included in this PR?
- add `sort_merge_join`.
<!--
There is no need to duplicate the description in the ticket here but it
is sometimes worth providing a summary of the individual changes in this
PR.

Example:
- Add `NestedLoopJoinExec`.
- Speed up `HashJoinExec`.
- Route joins to `NestedLoopJoinExec` if the outer input is sufficiently
small.
-->

# Are these changes tested?
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?

Example:
Yes.
-->
Yes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants