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

Large objects #2

Open
thruflo opened this issue Jan 18, 2022 · 0 comments
Open

Large objects #2

thruflo opened this issue Jan 18, 2022 · 0 comments
Labels
epic

Comments

@thruflo
Copy link
Contributor

thruflo commented Jan 18, 2022 •
edited

Currently, querying the contents of large objects (maps, sets) copies the whole object (e.g.: the whole set) to the client to read one of the members.

We need a strategy to resolve this, as discussed in the Paris workshop.
@thruflo thruflo added enhancement New feature or request epic labels Jan 18, 2022
@balegas balegas removed the enhancement New feature or request label Mar 21, 2022
v0idpwn added a commit that referenced this issue Jun 5, 2022
@v0idpwn
Fix register to_ops/2 always returning an empty list (#2)
e056182 
Assumes LWW behaviour on dirt_value/1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
epic
Projects
No open projects
Vaxine Roadmap
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thruflo @balegas