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

Export in database - what would be the way to do it? #189

Closed
panthony opened this issue Mar 30, 2018 · 4 comments
Closed

Export in database - what would be the way to do it? #189

panthony opened this issue Mar 30, 2018 · 4 comments
Labels

Comments

@panthony
Copy link

Thanks for this nice project,

I'm playing with it and now I'm trying to store the result of a crawl within a database and I noticed that the BaseExporter expect the export to be in a file.

And I noticed that you had DB export in mind (#15).

So what would be the proper way?

Use the onSuccess callback? Or have a BaseExporter agnostic from the support (and have a FileExporter on top).

@yujiosaka
Copy link
Owner

@panthony
Good point.
I suggest you using onSuccess callback now because It's way simpler.

I'd like to start thinking about making exporters to DB.
What kind of DBs you have in mind? I believe it should be schema-less, so the main candidate would be MongoDB for example.

@panthony
Copy link
Author

panthony commented Apr 2, 2018

@yujiosaka For my use case I had Bigtable in mind.

Ok, for now I'll just try with the onSuccess

@BubuAnabelas
Copy link

@panthony I'm not familiar with Bigtable, but since it's NoSQL perhaps JSONLineExporter could help. It writes to a file but since it's done through writable streams maybe it can be changed to pipe it to Bigtable.

@yujiosaka
Copy link
Owner

Closing this because the problem seems to be solved.
Feel free to open a new issue if you'd like support features to store crawled results to DBs by exporters

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants