You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "David Robinson (JIRA)" <ji...@apache.org> on 2017/07/13 21:00:01 UTC

[jira] [Comment Edited] (IGNITE-4191) Transactional support at the level of Ignite drivers and DML

    [ https://issues.apache.org/jira/browse/IGNITE-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086345#comment-16086345 ] 

David Robinson edited comment on IGNITE-4191 at 7/13/17 8:59 PM:
-----------------------------------------------------------------

Same problem as reported in this defect occurs when trying to use Sqoop to pull data from Ignite.
Same problem as reported in this defect occurs when trying to use DbSchema to connect and work with Ignite (http://www.dbschema.com/)


was (Author: drobin1437):
Same problem as reported in this defect occurs when trying to use Sqoop to pull data from Ignite.

> Transactional support at the level of Ignite drivers and DML
> ------------------------------------------------------------
>
>                 Key: IGNITE-4191
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4191
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>            Reporter: Denis Magda
>             Fix For: 2.2
>
>
> Presently there is no any way to execute data modification statements and SELECT queries in a transactional fashion using our JDBC/ODBC drivers and DML API.
> This can be fully supported once MVCC is ready and released.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)