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

Namespace memory image #8

Open
johnny-morrice opened this issue Jul 22, 2017 · 0 comments
Open

Namespace memory image #8

johnny-morrice opened this issue Jul 22, 2017 · 0 comments
Assignees
Milestone

Comments

@johnny-morrice
Copy link
Owner

johnny-morrice commented Jul 22, 2017

We currently support a fast memory image for indices.

Decoupling the application state from IPFS allows us to perform joins (write queries) in parallel.

However, we still always write to IPFS for the namespaces.

Whether or not the namespace (and its index) will be written to IPFS should be controlled by a flag on api.Request. If the namespace will be directly written to IPFS, the path to an index for that namespace should be returned to the user. Otherwise, the namespace will remain cached until a write during the application pulse.

@johnny-morrice johnny-morrice added this to the 0.20.0 milestone Jul 22, 2017
@johnny-morrice johnny-morrice self-assigned this Jul 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant