[
https://issues.apache.org/jira/browse/TRAFODION-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16692053#comment-16692053
]
ASF GitHub Bot commented on TRAFODION-3235:
-------------------------------------------
Github user DaveBirdsall commented on a diff in the pull request:
https://github.com/apache/trafodion/pull/1747#discussion_r234716204
--- Diff: core/conn/odb/src/odb.c ---
@@ -10076,6 +10114,7 @@ static int Oloadbuff(int eid)
clock_gettime(CLOCK_MONOTONIC, &tsp1);
#endif
Or = SQLExecute(thps[tid].Os) ; /* Execute INSERT
(load/copy) or tgt command */
+ SQLLEN tLastRow = -1; /* this is special solution for
China Union Pay, print only first error message for state 22003 */
--- End diff --
Probably best not to put customer names into the code. Consider changing
the comment to just "/* print only first error message for state 22003 */"
> add div and trim function for map feature, improve bad file print function.
> ----------------------------------------------------------------------------
>
> Key: TRAFODION-3235
> URL: https://issues.apache.org/jira/browse/TRAFODION-3235
> Project: Apache Trafodion
> Issue Type: New Feature
> Components: db-utility-odb
> Reporter: 苏锦佩
> Assignee: 苏锦佩
> Priority: Major
>
> In some customer scenarios, they want below feature:
> # Div function in the map file, so the numeric data in the data file can be
> divided with some value before loading to the database. for example, we have
> a COL NUMERIC(6,2) column and the data '123456' in the data file, we can use
> the mapping rule 'COL:<field>\DIV:100' to translate the data to '1234.56'
> before loading to the database.
> # Trim function in the map file, so if some field containing leading and
> trailing space in the data file can be trimmed before loading to the
> database. for example, suppose we have a COL CHAR(20) and the data ' abc
> ' in the data file, we can use the mapping rule 'COL:<field>:TRIM' to
> translate the data to 'abc' before loading to the database.
> # Now, the odb tool will print a record for each ODBC error message in the
> bad file. But some bad row may report more than one error message, so the bad
> file may contain duplicated records. So add a fix to ensure that one bad
> record only printed once in bad file.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
