You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, first of all congratulations for the work done, i have had the opportunity to try your JDBC driver for a long time and i wanted to know more about future developments.
In particular, do you think it is possible to interrogate Kafka instead of KsqlDB?
To my knowledge Kafka does not expose an SQL query engine per se.
I see that your driver also works well with KsqlDB version 0.9, soon there will be the release of version 0.10 and with it most likely the new Java client (Source code)(Documentation).
In my opinion this client promises well with respect to the use of the Rest API, both on the performance side and because it exposes native methods for things like terminating queries after a certain period of time.
I'd like to hear your opinions.
The text was updated successfully, but these errors were encountered:
This driver was born in a very early stage of KSQL, providing another way to consume messages from Kafka via KSQL. The idea is still maintain the integration with KSQL (and not with Kafka).
KSQL is evolving a lot and based on this (see KLIP-15) the new API or whatever new feature included should be integrated within the driver but not integrating directly with KSQL (due to scalability and performance).
Hello, first of all congratulations for the work done, i have had the opportunity to try your JDBC driver for a long time and i wanted to know more about future developments.
In particular, do you think it is possible to interrogate Kafka instead of KsqlDB?
To my knowledge Kafka does not expose an SQL query engine per se.
I see that your driver also works well with KsqlDB version 0.9, soon there will be the release of version 0.10 and with it most likely the new Java client (Source code)(Documentation).
In my opinion this client promises well with respect to the use of the Rest API, both on the performance side and because it exposes native methods for things like terminating queries after a certain period of time.
I'd like to hear your opinions.
The text was updated successfully, but these errors were encountered: