therapon

Re:Timelines: Declarative, Temporal Queries on Tuesday May 30, 2023 @02:18PM (#36128438)

This is the second in a series of posts about Kaskada timelines. The highlight of this post is how timelines and the query language build on timelines helps write intuitive temporal queries over event based data.

We would be very interested in comments, thoughts, questions from the community.

-- Theo

Timelines: Declarative, Temporal Queries

Posted by therapon on Tuesday May 30, 2023 @02:18PM
from the kaskada.io dept.

https://kaskada.io/2023/05/25/introducing-timelines-part-2.html

( Read More... | 3 comments | 2 points | on HN )

Re:Timelines: An Evolution in Stream Processing Abstraction on Tuesday May 09, 2023 @01:46PM (#35877897)

We are very excited to have our 1st blog post in a series of blog posts talking about the recent work we are doing on Kaskada and on event based data processing. Kaskada was recently open sourced as well and if you are interested drop by https://github.com/kaskada-ai/kaskada

Timelines: An Evolution in Stream Processing Abstraction

Posted by therapon on Tuesday May 09, 2023 @01:46PM
from the kaskada.io dept.

https://kaskada.io/2023/05/09/introducing-timelines-part-1.html

( Read More... | 2 comments | 5 points | on HN )

Re:PartiQL: One query language for all your data on Friday August 02, 2019 @02:05AM (#20590926)

It looks like the first query run in the REPL takes more time (startup cost). Subsequent runs of that query return around 5ms. Even a query like `SELECT * FROM 1` when executed immediately after starting the REPL will take longer than usual. Even running non-query expression, e.g., `1 + 1` immediately after starting the REPL will take more time to complete than usual.

The time reported by the REPL can be misleading.

There is work that we definitely need to do on performance as we develop PartiQL. Performance is something we have been considering since inception and we will keep considering as we go forward.