Datatype NUMBER(22,4) is not regonized as valid data type while exporting data from teradata

[atulkakade]

Currently while exporting data when we have a data type of Number the Export fail with an error : Cannot determine data type. Are there any plan to add it to the export as Decimal type

here is sample test table

CREATE MULTISET TABLE dwp_sandbox.DW_PO_TUX_HDR_test2 ,NO FALLBACK ,
NO BEFORE JOURNAL,
NO AFTER JOURNAL,
CHECKSUM = DEFAULT,
DEFAULT MERGEBLOCKRATIO
(
Q_PO_HDR_ID VARCHAR(50) CHARACTER SET LATIN NOT CASESPECIFIC,
PO_TOTAL_AMT NUMBER(22,4)
)
PRIMARY INDEX ( Q_PO_HDR_ID )

[ChrisRx]

Is this using giraffez.BulkExport or giraffez export ...? If so, then I believe that the issue may be that the underlying Teradata driver/protocol, FastExport, probably doesn't support the Number data type.

[atulkakade]

Both . We have the same machine running tpt and fast exports using Teradata cli and we haven’t seen this issues with those utilities . Drivercersoon 15.10

[ChrisRx]

Can you give the full traceback for the error? Everything seems to point to it not being supported by the Teradata drivers (it is possible the Teradata drivers translate Number to BIGNUM instead?)

[atulkakade]

We are using the bulkexport via python scripts . We are able to export using Teradata tpt /fast export , but not via giraffez Thanks, Atul Kakade

…

On Nov 6, 2018, at 07:42, Chris Marshall ***@***.***> wrote: Is this using giraffez.BulkExport or giraffez export ...? If so, then I believe that the issue may be that the underlying Teradata driver/protocol, FastExport, probably doesn't support the Number data type. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[ChrisRx]

If you would provide the python exception traceback that would be a helpful start to looking at this.