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

fix(Dgraph): Don't store start_ts in postings #6206

Merged
merged 1 commit into from Aug 17, 2020
Merged

Conversation

martinmr
Copy link
Contributor

@martinmr martinmr commented Aug 17, 2020

Clear out the start_ts field in the postings of deltas before they are
marshalled to avoid storing that field in disk. This field is only meant
to be used during in-memory processing.

Related to https://discuss.dgraph.io/t/start-ts-not-being-cleared-before-postings-are-written-to-disk/9146


This change is Reviewable

Clear out the start_ts field in the postings of deltas before they are
marshalled to avoid storing that field in disk. This field is only meant
to be used during in-memory processing.

Related to https://discuss.dgraph.io/t/start-ts-not-being-cleared-before-postings-are-written-to-disk/9146
@martinmr martinmr changed the title fix(Dgraph): Don't store start_ts in postings. (#6127) fix(Dgraph): Don't store start_ts in postings Aug 17, 2020
@martinmr
Copy link
Contributor Author

The previous PR didn't work because I was using a read lock to modify the protobufs. I verified that the TestConcurrentQueryMutate test runs fine by running it 50 times.

Copy link
Contributor

@parasssh parasssh left a comment

Choose a reason for hiding this comment

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

Thanks. Also, since this is an enhancement, it will have to wait for CP to prior release.

@martinmr
Copy link
Contributor Author

Ok. I'll open the cherry-picks today so I don't forget but I won't push them until the releases are out.

@martinmr martinmr merged commit fbbd731 into master Aug 17, 2020
@martinmr martinmr deleted the martinmr/start-ts branch August 17, 2020 22:57
martinmr added a commit that referenced this pull request Aug 17, 2020
Clear out the start_ts field in the postings of deltas before they are
marshalled to avoid storing that field in disk. This field is only meant
to be used during in-memory processing.

Related to https://discuss.dgraph.io/t/start-ts-not-being-cleared-before-postings-are-written-to-disk/9146

(cherry picked from commit fbbd731)
martinmr added a commit that referenced this pull request Aug 17, 2020
Clear out the start_ts field in the postings of deltas before they are
marshalled to avoid storing that field in disk. This field is only meant
to be used during in-memory processing.

Related to https://discuss.dgraph.io/t/start-ts-not-being-cleared-before-postings-are-written-to-disk/9146

(cherry picked from commit fbbd731)
martinmr added a commit that referenced this pull request Aug 17, 2020
Clear out the start_ts field in the postings of deltas before they are
marshalled to avoid storing that field in disk. This field is only meant
to be used during in-memory processing.

Related to https://discuss.dgraph.io/t/start-ts-not-being-cleared-before-postings-are-written-to-disk/9146

(cherry picked from commit fbbd731)
parasssh pushed a commit that referenced this pull request Aug 28, 2020
Clear out the start_ts field in the postings of deltas before they are
marshalled to avoid storing that field in disk. This field is only meant
to be used during in-memory processing.

Related to https://discuss.dgraph.io/t/start-ts-not-being-cleared-before-postings-are-written-to-disk/9146

(cherry picked from commit fbbd731)
parasssh pushed a commit that referenced this pull request Aug 31, 2020
Clear out the start_ts field in the postings of deltas before they are
marshalled to avoid storing that field in disk. This field is only meant
to be used during in-memory processing.

Related to https://discuss.dgraph.io/t/start-ts-not-being-cleared-before-postings-are-written-to-disk/9146

(cherry picked from commit fbbd731)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants