GitHub user selvaganesang opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/15

    Changes related to JIRA [TRAFODION-14]

    upsert or merge into a table with indexes can result in
    inconsistency between index and table
    
    The change is to pass the recent row timestamp to the Delete
    operator. However, this may not solve the above issue because
    tombstone marker timestamp can be same or later than the
    recently added row even with this change.
    
    This change is pushed for the following reasons:
    a) To enable Trafodion async operation concept for the merge
       operation
    b) To optimize delete operation by removing unwanted memory
       allocation.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/selvaganesang/incubator-trafodion master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafodion/pull/15.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #15
    
----
commit 960b8609fe94ad1c7d354545fde0dcafc81e6cbf
Author: selvaganesang <[email protected]>
Date:   2015-06-30T21:11:52Z

    Changes related to JIRA [TRAFODION-14]
    
    upsert or merge into a table with indexes can result in
    inconsistency between index and table
    
    The change is to pass the recent row timestamp to the Delete
    operator. However, this may not solve the above issue because
    tombstone marker timestamp can be same or later than the
    recently added row even with this change.
    
    This change is pushed for the following reasons:
    a) To enable Trafodion async operation concept for the merge
       operation
    b) To optimize delete operation by removing unwanted memory
       allocation.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to