[
https://issues.apache.org/jira/browse/IGNITE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15682871#comment-15682871
]
Alexander Paschenko commented on IGNITE-2294:
---------------------------------------------
Fixed all comments and failing tests. Waiting for results of post-fix full TC
run (in progress now).
I suggest that we leave alone {{JdbcQueryTaskV2}} with its UUID as long as this
UUID is also used in {{JdbcResultSet}}. Currently UUID in old {{JdbcQueryTask}}
does not seem to make any problems right away, so I think it would be better to
shift this UUID -> IgniteUuid transition till 2.0 is released - by that time,
we'll be able to fix all related classes in the right way without worrying
about breaking anything.
> Implement SQL DML (insert, update, delete) clauses.
> ---------------------------------------------------
>
> Key: IGNITE-2294
> URL: https://issues.apache.org/jira/browse/IGNITE-2294
> Project: Ignite
> Issue Type: Wish
> Reporter: Sergi Vladykin
> Assignee: Alexander Paschenko
> Labels: important
> Fix For: 1.8
>
>
> We need to add parsing for all the listed SQL commands and translate them
> into respective cache operations (putIfAbstent, put, remove).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
