KSQL: Open Source Streaming SQL for Apache Kafka
confluent.io
KSQL: Open Source Streaming SQL for Apache Kafka
1–10 of 87 posts
Re: KSQL: Open Source Streaming SQL for Apache Kafka
#2RethinkDB, as far as I understand, does the same thing - their changefeed mechanism would consume the DB log and run the queries against the log.
[1]: http://debezium.io
Re: KSQL: Open Source Streaming SQL for Apache Kafka
#3Re: KSQL: Open Source Streaming SQL for Apache Kafka
#4[1] https://medium.com/@mustafaakin/flink-streaming-sql-example-...
[2] https://ci.apache.org/projects/flink/flink-docs-release-1.3/...
Re: KSQL: Open Source Streaming SQL for Apache Kafka
#5Anyways, if anyone's wondering, here's the Github page. [1]
Also from FAQ [2]:
Is KSQL fully compliant to ANSI SQL?
KSQL is a dialect inspired by ANSI SQL. It has some differences because it is geared at processing streaming data. For example, ANSI SQL has no notion of “windowing” for use cases such as performing aggregations on data grouped into 5-minute windows, which is a commonly required functionality in the streaming world.
[1] https://github.com/confluentinc/ksql/blob/0.1.x/docs/syntax-...
[2] https://github.com/confluentinc/ksql/blob/0.1.x/docs/faq.md#...
Re: KSQL: Open Source Streaming SQL for Apache Kafka
#6Suppose you modeled your domain with events and your stack is build on top of it. As stuff happens in your application, events are generated and appended to the stream. The stream is consumed by any number of consumers and awesome stuff is produced with it. The stream is persisted and you have all events starting from day 1.
Over time, things have changed and you have evolved your events to include some fields and deprecate others. You could do this without any downtime whatsoever by changing your events in a way that is backward compatible way.
What is the good approach to what I'd call a `replay`?
When you want to replay all events, the version of your apps that will consume the events may not know about the fields that were in the event for day one.
Re: KSQL: Open Source Streaming SQL for Apache Kafka
#7Re: KSQL: Open Source Streaming SQL for Apache Kafka
#8I've had the question for a while so I'll ask it here, maybe someone can help me. Suppose you modeled your domain with events and your stack is build on top of it. As stuff happens in your application, events are generated and appended to the stream. The stream is consumed by any number of consumers and awesome stuff is produced with it. The stream is persisted and you have all events starting from day 1. Over time,…
Re: KSQL: Open Source Streaming SQL for Apache Kafka
#9I've had the question for a while so I'll ask it here, maybe someone can help me. Suppose you modeled your domain with events and your stack is build on top of it. As stuff happens in your application, events are generated and appended to the stream. The stream is consumed by any number of consumers and awesome stuff is produced with it. The stream is persisted and you have all events starting from day 1. Over time,…
Re: KSQL: Open Source Streaming SQL for Apache Kafka
#10I've had the question for a while so I'll ask it here, maybe someone can help me. Suppose you modeled your domain with events and your stack is build on top of it. As stuff happens in your application, events are generated and appended to the stream. The stream is consumed by any number of consumers and awesome stuff is produced with it. The stream is persisted and you have all events starting from day 1. Over time,…
I encountered that problem. The ad hoc fix, was to have a version field in each event and functions that translate the old event into new event(s). The code that processes the events only processes events of the current version. If your old events had been denormalized this might result into repetition of events when splitted.