There is no single implementation of Calcite's engine. (Well, the Enumerable convention is included in core, and implements the relational operators by generating Java iterators, but it doesn't store data on disk, and it's not a transactional engine.)
This issue is intended to allow an engine that supports transactions to surface them. To date, no engine has done that. On Tue, Feb 10, 2015 at 6:07 PM, Chin Wei Low <[email protected]> wrote: > Hi, > > I saw transaction support is stated in > https://issues.apache.org/jira/browse/CALCITE-18, with the description > ---- > *Low priority, but would be nice to have the driver expose the commit, > rollback, and savepoint methods to the underlying implementation. So the > implementation can have the ability to implement them if needed.* > ---- > > So, does that mean that transaction support has been implemented in Calcite > core, just that it is not expose in the driver? > > Regards, > Chin Wei
