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

Make the updates/inserts idempotent on access keys #33

Closed
frol opened this issue Oct 28, 2020 · 1 comment · Fixed by #47
Closed

Make the updates/inserts idempotent on access keys #33

frol opened this issue Oct 28, 2020 · 1 comment · Fixed by #47
Assignees
@khorolets
Labels
enhancement New feature or request indexer
Milestone
[Current] Mainnet...

Comments

@frol
Copy link
Contributor

frol commented Oct 28, 2020

Come up with the solution to make the updates/inserts idempotent to avoid the situation when two concurrent nodes may rewrite each other changes

See #32 for details
@frol frol added the enhancement New feature or request label Oct 28, 2020
khorolets added a commit that referenced this issue Nov 13, 2020
@khorolets
Fixes #33: Make the updates/inserts idempotent on access keys
ee45b24
@khorolets khorolets mentioned this issue Nov 13, 2020
Merged
frol pushed a commit that referenced this issue Nov 13, 2020
@khorolets @frol
Fixes #33: Make the updates/inserts idempotent on access keys
1897d4b
@khorolets
Copy link
Member

Closed by #47

khorolets added a commit that referenced this issue Dec 7, 2020
@khorolets
Fixes #33: Make the updates/inserts idempotent on access keys
b2cf3fb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@khorolets khorolets

Labels
enhancement New feature or request indexer
Projects
None yet
Milestone
[Current] Mainnet Guild 2020.11.02-20...
Development

Successfully merging a pull request may close this issue.

refactor: Make the updates/inserts idempotent on access keys near/near-indexer-for-explorer
2 participants
@frol @khorolets