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

[jira] [Work started] (TRAFODION-1747) Avoid generating and removing SQL errors in object id lookup

     [ https://issues.apache.org/jira/browse/TRAFODION-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on TRAFODION-1747 started by Hans Zeller.
----------------------------------------------
> Avoid generating and removing SQL errors in object id lookup
> ------------------------------------------------------------
>
>                 Key: TRAFODION-1747
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-1747
>             Project: Apache Trafodion
>          Issue Type: Improvement
>          Components: sql-cmp
>    Affects Versions: 2.0-incubating
>            Reporter: Hans Zeller
>            Assignee: Hans Zeller
>            Priority: Minor
>             Fix For: 2.0-incubating
>
>
> I often debug code by setting a breakpoint at ComDiagsArea::insertNewError(). Lately I noticed that we hit this error in successful statements, due to a method that tries to find out whether a Hive table has been registered in Trafodion.
> This change avoids putting these errors in the SQL diagnostics area and then removing them again and it will make debugging easier (at least for me).



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