[
https://issues.apache.org/jira/browse/TRAFODION-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351444#comment-15351444
]
ASF GitHub Bot commented on TRAFODION-1988:
-------------------------------------------
Github user DaveBirdsall commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/559#discussion_r68619686
--- Diff:
core/sqf/src/seatrans/tm/hbasetmlib2/src/main/java/org/trafodion/dtm/TmAuditTlog.java
---
@@ -961,18 +814,14 @@ public static boolean deleteRecord(final long
lvTransid) throws IOException {
if (LOG.isTraceEnabled()) LOG.trace("deleteRecord start " +
lvTransid);
String transidString = new String(String.valueOf(lvTransid));
int lv_lockIndex = (int)(lvTransid & tLogHashKey);
- try {
+ //try {
--- End diff --
Maybe should remove this comment? (since the corresponding catch block was
removed)
> 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)
