[
https://issues.apache.org/jira/browse/IGNITE-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814552#comment-15814552
]
Alexander Paschenko commented on IGNITE-4489:
---------------------------------------------
Re-structured the code for better maintainability (split
{{DmlStatementsProcessor}} that started getting huge into classes that
encompass logic of INSERT, UPDATE, and MERGE); added a test. Started TC tests,
after they pass will convert this to *patch available*.
I also suggest that we release fixes for this, as well as IGNITE-4363 and
IGNITE-4490 in a single branch (corresponding to this issue) as long as this
looks like a major improvement and and the same time depends on fixes from
aforementioned branches. [~vozerov]
> 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: 2.0
>
>
> 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)
