[
https://issues.apache.org/jira/browse/IGNITE-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15785723#comment-15785723
]
Alexander Paschenko commented on IGNITE-4489:
---------------------------------------------
While conceiving better MERGE, I came across a great optimization opportunity.
As a result, in last few days I've mostly rewritten all routines in
DmlStatementProcessor whilst moving most of actual operations logic to
EntryProcessors to better distribute burden of building new values - now, only
keys get built on the node that processes the query, and values are constructed
and processed as needed by corresponding operations' semantic on the nodes
corresponding to keys according to affinity function.
> 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)
