[
https://issues.apache.org/jira/browse/TRAFODION-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379707#comment-15379707
]
ASF GitHub Bot commented on TRAFODION-2109:
-------------------------------------------
Github user DaveBirdsall commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/593#discussion_r71007538
--- Diff: core/sql/executor/ExHbaseAccess.cpp ---
@@ -2967,22 +2968,28 @@ void ExHbaseAccessTcb::handleException(NAHeap *heap,
ComCondition *errorCond,
ExpHbaseInterface * ehi,
NABoolean & LoggingFileCreated,
- char *loggingFileName)
+ char *loggingFileName,
+ ComDiagsArea **loggingErrorDiags)
{
Lng32 errorMsgLen = 0;
charBuf *cBuf = NULL;
char *errorMsg;
Lng32 retcode;
+ if (*loggingErrorDiags != NULL)
--- End diff --
Not quite sure I understand this logic. If a ComDiagsArea object has
already been allocated, does that mean we have already reported the exception
somewhere else? Or perhaps this is not the first exception and we simply don't
want to log more than one?
> Load with log error rows returns the following error at times
> -------------------------------------------------------------
>
> Key: TRAFODION-2109
> URL: https://issues.apache.org/jira/browse/TRAFODION-2109
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-exe
> Affects Versions: 1.3-incubating
> Reporter: Selvaganesan Govindarajan
> Assignee: Selvaganesan Govindarajan
> Fix For: 2.1-incubating
>
>
> load with log error rows into <trafodion_table>
> select * from hive.hive.<hive_table>
> *** ERROR[2034] $Z0014JQ:5192: Operating system error 201 while communicating
> with server process $Z021FS0:425.
>
> *** ERROR[2034] $Z0014JQ:5192: Operating system error 201 while communicating
> with server process $Z021FS0:425.
>
> *** ERROR[2034] $Z0014JQ:5192: Operating system error 201 while communicating
> with server process $Z021FS0:425.
>
> --- 0 row(s) loaded.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
