GitHub user selvaganesang opened a pull request:

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

    Fix for [TRAFODION-14]

    upsert or merge into a table with indexes can result
    in inconsistency between index and table
    
    This change avoids the HBase issue of rows getting lost when the
     delete and put operations are done in the same milliseconds
    timestamp dimension for the given rowid.
    
    In the trafodion_delete operation execution, the row is skipped
    for deletion if the new and old rowid evaluates to the same value.
    
    This needs change from the compiler sub-task in the JIRA to complete
    for it to be effective.
    
    In addition removed yet another memory allocation for the delete
    operation.

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

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

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

    https://github.com/apache/incubator-trafodion/pull/32.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 #32
    
----
commit 23657930173e018bcccc9bb55f5ce154dbe51714
Author: Selva Govindarajan <[email protected]>
Date:   2015-07-21T01:18:18Z

    Fix for [TRAFODION-14]
    
    upsert or merge into a table with indexes can result
    in inconsistency between index and table
    
    This change avoids the HBase issue of rows getting lost when the
     delete and put operations are done in the same milliseconds
    timestamp dimension for the same rowid.
    
    In the trafodion_delete operation execution, the row is skipped
    for deletion if the new and old rowid evaluates to the same value.
    
    This needs change from the compiler sub-task in the JIRA to complete
    for it to be effective.
    
    In addition removed yet another memory allocation for the delete
    operation.

----


---
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