If client node based driver [1] is used, then you can also add transactionsAllowed=true parameter to URL to overcome this error.
This will NOT enable transactional support, but will force the driver to go through transaction related methods without exceptions. So for example, if there are several updates executed in a transaction, they will be actually executed as individual updates. Obviously this option should be used with care, and most likely not in production environments. But if you're testing integration of Ignite with some external tools, it can be useful until full transactional support is available. [1] https://apacheignite-sql.readme.io/docs/jdbc-client-driver -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
