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.

Sign up for GitHub

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

Jump to bottom

[occ] MVKV store implementation and tests #323

Merged
merged 8 commits into from
Oct 10, 2023
Merged

[occ] MVKV store implementation and tests #323

merged 8 commits into from
Oct 10, 2023

Conversation

udpatil
Copy link
Contributor

@udpatil udpatil commented Oct 3, 2023 •
edited
Loading

Describe your changes and provide context

This implements an mvkv store that will manage access from a transaction execution to the underlying multiversion store and underlying parent store if the multiversion store doesn't have that key. It will first serve any reads from its own writeset and readset, but if it does have to fall through to multiversion store or parent store, it will add those values to the readset.

Testing performed to validate your change

Unit tests

@udpatil udpatil changed the base branch from main to occ-main October 3, 2023 23:15
@udpatil udpatil marked this pull request as ready for review October 6, 2023 02:18
@udpatil udpatil force-pushed the occ-mvkv-store branch 5 times, most recently from c760575 to 8fdf959 Compare October 6, 2023 21:48
@udpatil udpatil merged commit 98c4fb4 into occ-main Oct 10, 2023
14 checks passed
@udpatil udpatil deleted the occ-mvkv-store branch October 10, 2023 19:30
udpatil added a commit that referenced this pull request Oct 17, 2023
@udpatil
[occ] MVKV store implementation and tests (#323)
8fad9b2 
## Describe your changes and provide context
This implements an mvkv store that will manage access from a transaction
execution to the underlying multiversion store and underlying parent
store if the multiversion store doesn't have that key. It will first
serve any reads from its own writeset and readset, but if it does have
to fall through to multiversion store or parent store, it will add those
values to the readset.

## Testing performed to validate your change
Unit tests
udpatil added a commit that referenced this pull request Oct 17, 2023
@udpatil
[occ] MVKV store implementation and tests (#323)
fbb7bc4 
## Describe your changes and provide context
This implements an mvkv store that will manage access from a transaction
execution to the underlying multiversion store and underlying parent
store if the multiversion store doesn't have that key. It will first
serve any reads from its own writeset and readset, but if it does have
to fall through to multiversion store or parent store, it will add those
values to the readset.

## Testing performed to validate your change
Unit tests
udpatil added a commit that referenced this pull request Oct 17, 2023
@udpatil
[occ] MVKV store implementation and tests (#323)
571d00a 
## Describe your changes and provide context
This implements an mvkv store that will manage access from a transaction
execution to the underlying multiversion store and underlying parent
store if the multiversion store doesn't have that key. It will first
serve any reads from its own writeset and readset, but if it does have
to fall through to multiversion store or parent store, it will add those
values to the readset.

## Testing performed to validate your change
Unit tests
udpatil added a commit that referenced this pull request Jan 2, 2024
@udpatil
[occ] MVKV store implementation and tests (#323)
03069b6 
## Describe your changes and provide context
This implements an mvkv store that will manage access from a transaction
execution to the underlying multiversion store and underlying parent
store if the multiversion store doesn't have that key. It will first
serve any reads from its own writeset and readset, but if it does have
to fall through to multiversion store or parent store, it will add those
values to the readset.

## Testing performed to validate your change
Unit tests
udpatil added a commit that referenced this pull request Jan 8, 2024
@udpatil
[occ] MVKV store implementation and tests (#323)
91c228a 
## Describe your changes and provide context
This implements an mvkv store that will manage access from a transaction
execution to the underlying multiversion store and underlying parent
store if the multiversion store doesn't have that key. It will first
serve any reads from its own writeset and readset, but if it does have
to fall through to multiversion store or parent store, it will add those
values to the readset.

## Testing performed to validate your change
Unit tests
udpatil added a commit that referenced this pull request Jan 18, 2024
@udpatil
[occ] MVKV store implementation and tests (#323)
fe9f8e8 
## Describe your changes and provide context
This implements an mvkv store that will manage access from a transaction
execution to the underlying multiversion store and underlying parent
store if the multiversion store doesn't have that key. It will first
serve any reads from its own writeset and readset, but if it does have
to fall through to multiversion store or parent store, it will add those
values to the readset.

## Testing performed to validate your change
Unit tests
udpatil added a commit that referenced this pull request Jan 18, 2024
@udpatil
[occ] MVKV store implementation and tests (#323)
78f16fd 
## Describe your changes and provide context
This implements an mvkv store that will manage access from a transaction
execution to the underlying multiversion store and underlying parent
store if the multiversion store doesn't have that key. It will first
serve any reads from its own writeset and readset, but if it does have
to fall through to multiversion store or parent store, it will add those
values to the readset.

## Testing performed to validate your change
Unit tests
udpatil added a commit that referenced this pull request Jan 25, 2024
@udpatil
[occ] MVKV store implementation and tests (#323)
ab27bcc 
## Describe your changes and provide context
This implements an mvkv store that will manage access from a transaction
execution to the underlying multiversion store and underlying parent
store if the multiversion store doesn't have that key. It will first
serve any reads from its own writeset and readset, but if it does have
to fall through to multiversion store or parent store, it will add those
values to the readset.

## Testing performed to validate your change
Unit tests
udpatil added a commit that referenced this pull request Jan 31, 2024
@udpatil
[occ] MVKV store implementation and tests (#323)
0520ced 
## Describe your changes and provide context
This implements an mvkv store that will manage access from a transaction
execution to the underlying multiversion store and underlying parent
store if the multiversion store doesn't have that key. It will first
serve any reads from its own writeset and readset, but if it does have
to fall through to multiversion store or parent store, it will add those
values to the readset.

## Testing performed to validate your change
Unit tests
codchen pushed a commit that referenced this pull request Feb 6, 2024
@udpatil @codchen
[occ] MVKV store implementation and tests (#323)
9e42a3b 
## Describe your changes and provide context
This implements an mvkv store that will manage access from a transaction
execution to the underlying multiversion store and underlying parent
store if the multiversion store doesn't have that key. It will first
serve any reads from its own writeset and readset, but if it does have
to fall through to multiversion store or parent store, it will add those
values to the readset.

## Testing performed to validate your change
Unit tests
udpatil added a commit that referenced this pull request Feb 27, 2024
@udpatil
[occ] MVKV store implementation and tests (#323)
783c046 
## Describe your changes and provide context
This implements an mvkv store that will manage access from a transaction
execution to the underlying multiversion store and underlying parent
store if the multiversion store doesn't have that key. It will first
serve any reads from its own writeset and readset, but if it does have
to fall through to multiversion store or parent store, it will add those
values to the readset.

## Testing performed to validate your change
Unit tests
udpatil added a commit that referenced this pull request Mar 1, 2024
@udpatil
[occ] MVKV store implementation and tests (#323)
d235725 
## Describe your changes and provide context
This implements an mvkv store that will manage access from a transaction
execution to the underlying multiversion store and underlying parent
store if the multiversion store doesn't have that key. It will first
serve any reads from its own writeset and readset, but if it does have
to fall through to multiversion store or parent store, it will add those
values to the readset.

## Testing performed to validate your change
Unit tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@stevenlanders stevenlanders stevenlanders approved these changes

@codchen codchen Awaiting requested review from codchen

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@udpatil @stevenlanders