You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexander Paschenko (JIRA)" <ji...@apache.org> on 2016/12/23 16:15:58 UTC

[jira] [Commented] (IGNITE-4489) Maintain correct MERGE semantic in DML

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

Alexander Paschenko commented on IGNITE-4489:
---------------------------------------------

Done with modifying object correctly; however, what's more complex is to perform cache update in a right way (when key is present, it becomes similar to UPDATE or DELETE - we have to use {{EntryProcessor}} s, working on it.

> Maintain correct MERGE semantic in DML
> --------------------------------------
>
>                 Key: IGNITE-4489
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4489
>             Project: Ignite
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 1.8
>            Reporter: Alexander Paschenko
>            Assignee: Alexander Paschenko
>             Fix For: 1.8
>
>
> Currently it's impossible to MERGE object in UPDATE style - i.e. when key is present in cache, unaffected field values should be retained, and instead of building new object we should base it on previous one for given key.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)