11–20 of 54 posts
If so, this could be an interesting alternative to RethinkDB's changefeeds, as RethinkDB doesn't support joins on the change stream.
What does ETL mean in this context?
Do Continuous Views work with table-table joins, or must there always be at least one stream present? The documentation[1] doesn't specify. If so, this could be an interesting alternative to RethinkDB's changefeeds, as RethinkDB doesn't support joins on the change stream. [1] http://docs.pipelinedb.com/joins.html
Our next release (2.1) is due in about three weeks and includes automatic failover/high availability. Feeds on table joins (and other greatly expanded feed functionality) will be in 2.2, which should happen ~6-8 weeks after 2.1.
(Sorry to jump in with a shameless plug; what PipelineDB is doing is super-cool; I also met the founders a few times, and they're awesome, smart, and very driven people -- I'm really excited about what PipelineDB has to offer!)
Do Continuous Views work with table-table joins, or must there always be at least one stream present? The documentation[1] doesn't specify. If so, this could be an interesting alternative to RethinkDB's changefeeds, as RethinkDB doesn't support joins on the change stream. [1] http://docs.pipelinedb.com/joins.html
Currently continuous views must read from a stream. However, in the very near future it will possible to write to streams from triggers, which would probably give you enough flexibility to model the behavior you want if you could conceptualize a table as a stream of changes.
Would it be possible to set triggers or something on the continuous views? Lets say I want to take action (immediately) when a value calculated over sliding window goes above a limit.
It's a bit late here but I'll definitely play with PipelineDB tomorrow.
It looks like PipelineDB is implemented as a fork of PostgreSQL. I would be interested to understand what is different about the architecture of PipelineDB that it couldn't be integrated into upstream PostgreSQL.
However, we love Postgres and plan on actively merging upstream releases!
This is awesome, thanks for making it open source! Would it be possible to set triggers or something on the continuous views? Lets say I want to take action (immediately) when a value calculated over sliding window goes above a limit. It's a bit late here but I'll definitely play with PipelineDB tomorrow.
Awesome--let us know what you think about it!
I was under the impression that the academic projects had proposed StreamSQL as a general language, though since StreamBase's acquisition it now seems to have been branded as TIBCO StreamSQL[2]. Have you guys been part of any efforts to make sure that there is an open language standard?
[1] http://streambase.typepad.com/streambase_stream_process/2013...
[2] http://www.streambase.com/developers/docs/latest/streamsql/