Calcite doesn’t have its own data, it’s true. But it has a SQL parser and JDBC driver, and it can execute queries using its Enumerable convention (basically, Java iterators). That makes it a federation engine. (And its strong support for materialized views make it a very good federation engine.) To the client, it looks like a database.
Julian > On May 17, 2017, at 8:49 AM, Muhammad Gelbana <[email protected]> wrote: > > Are you saying that Calcite would behave as a datasource for Tableau ? > Because Calacite isn't a datasource, it's a query planner and optimizer. > Please correct me if I'm wrong. > > *---------------------* > *Muhammad Gelbana* > http://www.linkedin.com/in/mgelbana > > On Tue, May 16, 2017 at 7:43 PM, aka.fe2s <[email protected]> wrote: > >> Hi, >> >> Anybody tried to use Tableau with ODBC-JDBC bridge on top of Calcite? >> Please share your experience if so. >>
