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

define a clear set of APIs #3

Open
ocean1 opened this issue Sep 5, 2018 · 0 comments
Open

define a clear set of APIs #3

ocean1 opened this issue Sep 5, 2018 · 0 comments
Milestone

Comments

@ocean1
Copy link
Collaborator

ocean1 commented Sep 5, 2018

We want to have a clear structure, which will require minimal tinkering with the internals of crave for simple analyses, but also make it easy to create more complex set of scripts.
We need to evaluate switching DB backend from a key-valued store --which we might still support for a limited set of operations-- to something else, document the db structure, and allow low level operations (this is useful when we scrape tons of data, and want to run part of the analysis as an aggregation pipeline, or map reduce operation).

@ocean1 ocean1 added this to the v0.4 milestone Sep 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant