Skip to content

test: distinct cache ignores rows with nulls#26306

Merged
hiltontj merged 1 commit intomainfrom
hiltontj/distinct-cache-null-test
Apr 22, 2025
Merged

test: distinct cache ignores rows with nulls#26306
hiltontj merged 1 commit intomainfrom
hiltontj/distinct-cache-null-test

Conversation

@hiltontj
Copy link
Copy Markdown
Contributor

Closes #25564

Adds a test that checks the behaviour of the distinct cache with respect to null values. Currently, the distinct cache ignores rows that have NULL for any of the cached columns.

@hiltontj hiltontj added the v3 label Apr 22, 2025
@hiltontj hiltontj requested a review from a team April 22, 2025 14:08
@hiltontj hiltontj self-assigned this Apr 22, 2025
cat.create_distinct_cache(
TestWriter::DB_NAME,
"bar",
Some("cache_money"),
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.

💵 😄

Copy link
Copy Markdown
Contributor

@praveen-influx praveen-influx left a comment

Choose a reason for hiding this comment

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

LGTM - but I'm not sure about the linked GH issue, if you choose to not merge this in that is fine.

@hiltontj hiltontj merged commit 59c87ae into main Apr 22, 2025
12 checks passed
@hiltontj
Copy link
Copy Markdown
Contributor Author

Thanks @praveen-influx - I merged for now, since this does check that the cache is fulfilling its original requirements. If we decide to allow NULL in the cache I can open a separate issue.

@hiltontj hiltontj deleted the hiltontj/distinct-cache-null-test branch May 28, 2025 17:03
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.

Additional testing on the distinct value cache

2 participants