Sqoop Data Types
When you use Sqoop, some variations apply in the processing. Sqoop supports a subset of data types that database vendors support.
Aurora Data Types
Informatica supports the following Aurora data types when you use Sqoop:
- •Binary
- •Bit
- •Blob (supported only for import)
- •Char
- •Date
- •Datetime
- •Decimal
- •Double
- •Enum
- •Float
- •Integer
- •Numeric
- •Real
- •Set
- •Text
- •Time
- •Timestamp
- •Varbinary
- •Varchar
IBM DB2 and DB2 for z/OS Data Types
Informatica supports the following IBM DB2 and DB2 for z/OS data types when you use Sqoop:
- •Bigint
- •Blob (supported only for import)
- •Char
- •Clob
- •Date
- •DBClob
- •DecFloat (supported only for import)
- •Decimal
- •Double (supported only for DB2 for z/OS)
- •Float (supported only for DB2)
- •Graphic
- •Integer
- •LongVargraphic (supported only for DB2)
- •Numeric
- •Real
- •Smallint
- •Time
- •Timestamp
- •Varchar
- •Vargraphic
- •XML (supported only for import)
Greenplum Data Types
Informatica supports the following Greenplum data types when you use Sqoop:
- •Bigint
- •Bigserial
- •Bytea
- •Date
- •Decimal
- •Double
- •Integer
- •Nchar
- •Numeric
- •Nvarchar
- •Real
- •Serial
- •Smallint
- •Text
- •Time
- •Timestamp
Microsoft SQL Server Data Types
Informatica supports the following Microsoft SQL Server data types when you use Sqoop:
- •Bigint
- •Bit
- •Char
- •Datetime
- •Decimal
- •Float
- •INT
- •Money
- •Numeric
- •Real
- •Smalldatetime
- •Smallint
- •Smallmoney
- •Text
- •Time
- •Tinyint
- •Varchar
Rules and Guidelines for Sqoop Microsoft SQL Server Data Types
Consider the following rules and guidelines when you configure Microsoft SQL Server data types in a Sqoop mapping:
- •If you create or replace the target table at run time and run the mapping on the Blaze or Spark engine to export Bigint data, the mapping fails.
- •If you run a Sqoop mapping to export time data, Sqoop does not export milliseconds.
Netezza Data Types
Informatica supports the following Netezza data types when you use Sqoop:
- •Bigint
- •Blob (supported only for import)
- •Byteint
- •Char
- •Date
- •Double
- •Float4
- •Float8
- •Number
- •Timestamp
- •Varchar
Oracle Data Types
Informatica supports the following Oracle data types when you use Sqoop:
- •Blob (supported only for import)
- •Char
- •Date
- •Float
- •Long
- •Nchar (supported if you configure OraOop)
- •Nvarchar (supported if you configure OraOop)
- •Number(P,S)
- •Timestamp
- •Varchar
- •Varchar2
Rules and Guidelines for Sqoop Oracle Data Types
Consider the following rules and guidelines when you configure Oracle data types in a Sqoop mapping:
- •If you run a Sqoop mapping on the Blaze engine to export Oracle float data, Sqoop truncates the data.
- •If you run a Sqoop mapping on the Blaze engine to export Oracle timestamp data with nanoseconds, Sqoop writes only three digits to the target.
- •If you configure OraOop and run a Sqoop mapping on the Spark engine to export Oracle timestamp data, Sqoop writes only three digits to the target.
Teradata Data Types
Informatica supports the following Teradata data types when you use Sqoop:
- •Bigint (supported only for import)
- •Blob (supported only for import)
- •Byteint
- •Char
- •Clob
- •Date
- •Decimal
- •Double
- •Float
- •Integer
- •Number
- •Numeric
- •Real
- •Smallint
- •Time
Note: If you run a Sqoop mapping to export time data, Sqoop does not export milliseconds.
- •Timestamp
- •Varchar
Teradata Data Types with TDCH Specialized Connectors for Sqoop
Informatica supports the following Teradata data types when you use the Cloudera Connector Powered by Teradata, Hortonworks Connector for Teradata, and MapR Connector for Teradata with Sqoop:
- •Bigint
- •Byte (supported only by Hortonworks Connector for Teradata and MapR Connector for Teradata)
- •Byteint
- •Character
- •Date
- •Decimal
- •Double Precision/Float/Real
- •Integer
- •Number(P,S)
- •Numeric
- •Smallint
- •Time (supported only by Cloudera Connector Powered by Teradata and Hortonworks Connector for Teradata)
- •Timestamp
- •Varchar
- •Varbyte (supported only by Hortonworks Connector for Teradata and MapR Connector for Teradata)