You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Trina Krug (JIRA)" <ji...@apache.org> on 2016/05/18 00:08:12 UTC

[jira] [Commented] (TRAFODION-1988) Better java exception handling in the java layer of Trafodion

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

Trina Krug commented on TRAFODION-1988:
---------------------------------------

Passed basic TM testing. 

1) Test case 1 : TM killed in the middle of transaction.  Transaction was aborted, table consistent.
2) Test case 2 : TM killed in the middle of commit processing.  Transaction was aborted, table consistent.
3) Test case 3 : Commit conflict.  Received appropriate error.  Table as expected.
4) Test case 4 : Regionserver killed in the middle of transaction.  Transaction aborted, table consistent.

> Better java exception handling in the java layer of Trafodion
> -------------------------------------------------------------
>
>                 Key: TRAFODION-1988
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-1988
>             Project: Apache Trafodion
>          Issue Type: Improvement
>          Components: dtm, sql-exe
>    Affects Versions: 2.1-incubating
>            Reporter: Selvaganesan Govindarajan
>            Assignee: Selvaganesan Govindarajan
>
> Java exceptions are not handled in consistent manner in Trafodion. The SQL interface layer in Trafodion is capable of displaying the entire java stack trace to the client application when an exception is raised in java portion of the Trafodion/Hbase/Hdfs stack. However, there are portions of the code in Trafodion where the exceptions are not handled in a consistent manner. This JIRA attempts to fix this.



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