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

Add a test for citus_shards where table names have spaces #7224

Merged
merged 2 commits into from
Oct 16, 2023

Conversation

JelteF
Copy link
Contributor

@JelteF JelteF commented Sep 25, 2023

There was a bug reported for previous versions of Citus where
shard_size was returning NULL for tables with spaces in them. It works
fine on the main branch though, but I'm still adding a test for this to
the main branch because it seems a good test to have.

There was a bug reported for previous versions of Citus where
shard_size was returning NULL for tables with spaces in them. It works
fine on the main branch though, but I'm still adding a test for this to
the main branch because it seems a good test to have.
@codecov
Copy link

codecov bot commented Sep 25, 2023

Codecov Report

Merging #7224 (f3819af) into main (fb08f9b) will increase coverage by 0.00%.
The diff coverage is n/a.

❗ Current head f3819af differs from pull request most recent head a7774c2. Consider uploading reports for the commit a7774c2 to get more accurate results

@@           Coverage Diff           @@
##             main    #7224   +/-   ##
=======================================
  Coverage   93.22%   93.22%           
=======================================
  Files         275      275           
  Lines       59494    59456   -38     
=======================================
- Hits        55464    55430   -34     
+ Misses       4030     4026    -4     

---------------------------------------------------------------------
"t with space" | 99456904 | citus_shards."t with space_99456904" | distributed | 456900 | localhost | 57637 | 40960
"t with space" | 99456905 | citus_shards."t with space_99456905" | distributed | 456900 | localhost | 57638 | 40960
"t with space" | 99456906 | citus_shards."t with space_99456906" | distributed | 456900 | localhost | 57637 | 40960
Copy link
Member

Choose a reason for hiding this comment

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

maybe reduce the columns to avoid flakiness

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The values don't cause flakiness because I reset the relevant sequences at the top of this test to the expected values. I'd rather keep all columns instead so we are actually testing that the the full view works.

Copy link
Collaborator

@marcoslot marcoslot Oct 13, 2023

Choose a reason for hiding this comment

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

Sizes can also have some variability, but maybe it's fine

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's fair, we usually start using a range there when they turn out to be variable. I think in this case it's not a problem. But to be clear, the sizes were specifically the issue with the tables with spaces, so I definitely want to include them.

@JelteF JelteF enabled auto-merge (squash) October 13, 2023 14:56
@JelteF JelteF merged commit 788e09a into main Oct 16, 2023
151 of 154 checks passed
@JelteF JelteF deleted the citus_shards-test branch October 16, 2023 09:38
francisjodi pushed a commit that referenced this pull request Nov 13, 2023
There was a bug reported for previous versions of Citus where
shard\_size was returning NULL for tables with spaces in them. It works
fine on the main branch though, but I'm still adding a test for this to
the main branch because it seems a good test to have.
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.

3 participants