[
https://issues.apache.org/jira/browse/TRAFODION-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839291#comment-15839291
]
ASF GitHub Bot commented on TRAFODION-2351:
-------------------------------------------
Github user selvaganesang commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/931#discussion_r97934559
--- Diff: core/sql/executor/ExExeUtilLoad.cpp ---
@@ -1442,7 +1442,8 @@ short ExExeUtilHBaseBulkLoadTcb::work()
ComCondition *cond;
Lng32 entryNumber;
while ((cond = diagsArea->findCondition(EXE_ERROR_ROWS_FOUND,
&entryNumber)) != NULL) {
- errorRowCount = cond->getOptionalInteger(0);
+ if (errorRowCount < cond->getOptionalInteger(0))
--- End diff --
Actually, the changes in ExHdfsScan.cpp is the one needed to take care of
the core dump issue. To honor the command 'stop after n error rows' when the
data is loaded into trafodion table, a counter is maintained in hbase to
increment the number of error rows from all the ESP process. Each load prepare
command has its own counter id. This counter id is visible to the
ExHbaseAccessBulkLoadPrepSQTcb operator. This operator hosted in multiple ESPs
will read the counter at the end of its operation and pass it as a warning. So
all the ESPs are expected to have the same value but if an esp finishes early
it may not have read the final counter value. Hence I am taking the max error
counter value passed in the warnings.
> Bulk load with log error rows enhancements
> ------------------------------------------
>
> Key: TRAFODION-2351
> URL: https://issues.apache.org/jira/browse/TRAFODION-2351
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-exe
> Reporter: Selvaganesan Govindarajan
> Assignee: Selvaganesan Govindarajan
>
> Bulk load needs the following enhancements
> 1) Load with log error rows misses out some error rows being logged
> 2) Load with log error rows need to report if there are any error rows
> 3) Load with log error rows need to report where the error rows are logged
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
