Fabian , looking at the response below again.. As I’m currently looking into the Batch mode only ( execution result mode = table ) I was thinking of wrapping the SQL CLI code with a Calcite Adapter might do the trick.
I don’t want to have a different execution engine ( like DRILL) just to allow ad hoc queries. And JDBC will allow me to use a lot of 3rd part display ( BI tools , notebooks , etc..). Do you believe its a viable solution while the JDBC and SQL GW is still work in progress ? -----Original Message----- From: Fabian Hueske <fhue...@gmail.com> Sent: 8 April 2019 11:18 To: dev <dev@flink.apache.org> Subject: Re: SQL CLI and JDBC Hi Hanan, I'm not aware of any plans to add a JDBC Driver. One issue with the JDBC interface is that it only works well for queries on batch data and a subset of queries on streaming data. Many streaming SQL queries are not able to emit final results (or need to update previously emitted results). Take for instance a query like SELECT colA, COUNT(*) FROM tab GROUP BY colA; If tab is a continuously growing table, no row of the queries result will ever be final because a new row with any value of colA can be added at any point in time. JDBC does not support to retract or update result rows that were emitted before. Best, Fabian Am So., 7. Apr. 2019 um 11:31 Uhr schrieb Hanan Yehudai < hanan.yehu...@radcom.com>: > I didn’t see any docs on this - is there a JDBC Driver that allows > the same functionalities as the SQL CLI ? > If not , is it on the roadmap ? > >
