Write Simple Processors to support the most common dbsSee original GitHub issue
A Processor is a partial function that process data from a stream and does something with it – see documentation for more information.
Wouldn’t be great having a set of predefined processors that save tweets from a stream for the most common used db? That would translate in implementing a function
PartialFunction[Tweet, Unit] where the side effect is saving in a db – probably with bulk update support?
NOTE: Not super simple but definitively fun and useful!
- Created 7 years ago
- Comments:6 (3 by maintainers)
Top GitHub Comments
I will work on this in the future.
As we discussed: Framework to use: Slick (v3.1.1) Entities to persist: Tweets
Design: For each table/entity, we need to create a table mapping and eventually a DAO. Possibly we need distinct mappings, one for SQL and another for NOSQL