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

Remove 256K page size limit for ftable #3266

Merged
merged 1 commit into from
Apr 15, 2024

Conversation

andyfengHKU
Copy link
Contributor

Fix issue #3246.

The core change is to force DataBlock to always take a size as a constructor parameter. In most of the cases this will be 256_PAGE_SIZE but we do allow allocating more than it.

As I'm writing the test, I realize the previous assumption (that a tuple is always small) still holds because an average column size is 16 bytes (considering their fixed size part) and we need more than 16K columns to exceed the limit.

What was problematic and being fixed in this PR is in unFlat tuple block where each block can hold 2048 tuples at max. In such case, we trigger limitation if a tuple has more than 128K in size (average 8 columns).

@andyfengHKU andyfengHKU force-pushed the remove-256K-page-size-for-ftable branch from f072045 to 5084ce7 Compare April 15, 2024 02:44
@andyfengHKU andyfengHKU merged commit 3600a93 into master Apr 15, 2024
17 checks passed
@andyfengHKU andyfengHKU deleted the remove-256K-page-size-for-ftable branch April 15, 2024 03:24
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.

None yet

2 participants