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

Proposal: Filters and big data API #17

Open
davisjam opened this issue Apr 10, 2018 · 0 comments
Open

Proposal: Filters and big data API #17

davisjam opened this issue Apr 10, 2018 · 0 comments

Comments

@davisjam
Copy link

This is a proposal, not a bug report. As such it's a bit unfocused, mostly brainstorming.

  • Filter the package.jsons from meta/
  • Filter the .tgzs from current/, optionally based on the filtered package.json's from meta/

This is similar to the code search and AST execute APIs, but seems more general-purpose.

I know I can grep through the files in pool/ for this, but that's brittle because it depends on Gzemnid internals. Can Gzemnid expose this facility?

Also, Gzemnid queries are a big data problem. Thoughts on exposing some kind of producer-consumer web API so I can easily distribute queries across a cluster of workers?

I'm happy to work on a PR if we can decide on the API (e.g. celery or similar).

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