Skip to content
New issue

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

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

Already on GitHub? # to your account

fix(stream): improve incremental stream writer #1901

Merged
merged 1 commit into from
Jun 12, 2023
Merged

fix(stream): improve incremental stream writer #1901

merged 1 commit into from
Jun 12, 2023

Conversation

mangalaman93
Copy link
Contributor

@mangalaman93 mangalaman93 commented Mar 7, 2023

This commit fails incremental stream writer if memtable has data. It also allows calling incremental stream store more times than the number of levels we have. This is done by calling Flatten when we have reached L0 and incremental stream writer can be used again.

@mangalaman93 mangalaman93 force-pushed the aman/bug branch 3 times, most recently from fef30d6 to f330119 Compare March 8, 2023 00:05
@mangalaman93 mangalaman93 changed the title fix(stream): fail incremental stream writer if mem table has data fix(stream): improve incremental stream writer Mar 8, 2023
Copy link
Contributor

@joshua-goldstein joshua-goldstein left a comment

Choose a reason for hiding this comment

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

Looks good! Let's get #1908 in first so Dgraph tests run against this (don't think there is an issue but it will be good to see the workflow run).

This commit fails incremental stream writer if memtable has data.
It also allows calling incremental stream writer  more times than
the number of levels we have. This is done by calling Flatten
when we have want to write and L0 already has data.
@mangalaman93 mangalaman93 merged commit 1425208 into main Jun 12, 2023
@mangalaman93 mangalaman93 deleted the aman/bug branch June 12, 2023 04:37
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants