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

test: Multi-column index selection through query macro #1001

Merged
merged 1 commit into from
Mar 21, 2024

Conversation

joshua-spacetime
Copy link
Collaborator

Description of Changes

Please describe your change, mention any related tickets, and so on here.

API and ABI breaking changes

If this is an API or ABI breaking change, please apply the
corresponding GitHub label.

Expected complexity level and risk

How complicated do you think these changes are? Grade on a scale from 1 to 5,
where 1 is a trivial change, and 5 is a deep-reaching and complex change.

This complexity rating applies not only to the complexity apparent in the diff,
but also to its interactions with existing and future code.

If you answered more than a 2, explain what is complex about the PR,
and what other components it interacts with in potentially concerning ways.

Testing

Describe any testing you've done, and any testing you'd like your reviewers to do,
so that you're confident that all the changes work as expected!

  • Write a test you've completed here.
  • Write a test you want a reviewer to do here, so they can check it off when they're satisfied.

Copy link
Contributor

@gefjon gefjon left a comment

Choose a reason for hiding this comment

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

Could you add a README.md in the new module which says which test it's used for? I know we haven't been very good about including these so far, but I'd at least like to have them for any new modules we add.

@joshua-spacetime joshua-spacetime force-pushed the joshua/test/multi-col-index-selection branch 3 times, most recently from 871de66 to 5455430 Compare March 21, 2024 19:55
@@ -234,8 +237,6 @@ impl PointerMap {
///
/// Handles any hash conflicts for `hash`.
pub fn insert(&mut self, hash: RowHash, ptr: RowPointer) -> bool {
debug_assert!(self.maintains_invariants());
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I'm not sure why these were left in, but they make populating a table quadratic time.

Copy link
Contributor

Choose a reason for hiding this comment

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

Were these a problem in terms of the runtime of tests? Otherwise, these are in the debug profile only and are used to test an invariant that unsafe code assumes.

let json = r#"{"call": {"fn": "test_index_scan_on_chunk", "args": []}}"#;
module.send(json.to_string()).await.unwrap();

let json = r#"{"call": {"fn": "test_index_scan_on_x_z_dimension", "args": []}}"#;
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This test will not pass without #1012

@joshua-spacetime joshua-spacetime force-pushed the joshua/test/multi-col-index-selection branch from 5455430 to 9982dcf Compare March 21, 2024 20:38
Copy link
Contributor

@mamcx mamcx left a comment

Choose a reason for hiding this comment

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

LGTM

@joshua-spacetime joshua-spacetime force-pushed the joshua/test/multi-col-index-selection branch from 9982dcf to 18f7b08 Compare March 21, 2024 23:16
@joshua-spacetime joshua-spacetime added this pull request to the merge queue Mar 21, 2024
Merged via the queue into master with commit 47e7878 Mar 21, 2024
6 checks passed
@joshua-spacetime joshua-spacetime deleted the joshua/test/multi-col-index-selection branch March 21, 2024 23:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants