[
https://issues.apache.org/jira/browse/TRAFODION-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092370#comment-15092370
]
ASF GitHub Bot commented on TRAFODION-1747:
-------------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-trafodion/pull/254
> 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)
