[
https://issues.apache.org/jira/browse/TRAFODION-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088591#comment-15088591
]
ASF GitHub Bot commented on TRAFODION-1747:
-------------------------------------------
GitHub user zellerh opened a pull request:
https://github.com/apache/incubator-trafodion/pull/254
[TRAFODION-1747] Avoid generating SQL errors in successful statements.
Using the "reportError" parameter in the underlying method to avoid
generating an error when we just want to test whether a certain
object name is registered in the OBJECTS table.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zellerh/incubator-trafodion bug/1581
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-trafodion/pull/254.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 #254
----
commit 9359d88f426bc944624028ee893e156cee4e706c
Author: Hans Zeller <hzel...@apache.org>
Date: 2016-01-08T02:09:24Z
[TRAFODION-1747] Avoid generating SQL errors in successful statements.
Using the "reportError" parameter in the underlying method to avoid
generating an error when we just want to test whether a certain
object name is registered in the OBJECTS table.
----
> 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)
