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

Storage format: Indexation direction #113

Open
d-r-q opened this issue May 30, 2020 · 0 comments
Open

Storage format: Indexation direction #113

d-r-q opened this issue May 30, 2020 · 0 comments
Labels
choose Issues, where there are several alternatives to consider and choose refactoring
Milestone

Comments

@d-r-q
Copy link
Owner

d-r-q commented May 30, 2020

Currently qbit performs initial wal indexation in backwards order (from leaf to root). But this approach has several disadvantages:

  • At the begin of an indexation, there is no information about db schema
  • It worse matches (probable) patches storage (Storage format: full entity vs patch #9)
  • It requires to store tombstones in index, to prevent insertion of deleted entitiies

The main advantage of this approach is that it doesn't require mutable forward trx graph index.
Also backward indexation may use immutable information from merge nodes about merged branches base.

On other hand current "backward" indexation, actually traverses a graph in backward direction and builts subgraph to index, and then traverses that graph in forward direction.

Consider switch to forward indexation direction. Especially, if #112 with append will be implemented.

@d-r-q d-r-q added choose Issues, where there are several alternatives to consider and choose refactoring labels May 30, 2020
@d-r-q d-r-q added this to the Backlog milestone May 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
choose Issues, where there are several alternatives to consider and choose refactoring
Projects
None yet
Development

No branches or pull requests

1 participant