To support communication between an OData client and a backend data store, Hybrid Data Pipeline uses a schema map to convert data to the appropriate type for the receiver. You configure the schema map in Hybrid Data Pipeline where it is generated as a JSON string with the following OData Entity Data Model (EDM) types.

Table 1. Supported Data Types
SQL Data Type EDM Data Type
BIGINT Edm.Int64
BINARY Edm.Binary
BIT Edm.Boolean
BLOB1 Edm.Binary
BOOLEAN Edm.Boolean
CHAR Edm.String
CLOB2 Edm.String
DATE Edm.Date
DECIMAL Edm.Decimal
DOUBLE Edm.Double
FLOAT Edm.Double
INTEGER Edm.Int32
LONGNVARCHAR2 Edm.String
LONGVARBINARY1 Edm.Binary
LONGVARCHAR2 Edm.String
NCLOB2 Edm.String
REAL Edm.Single
SMALLINT Edm.Int16
TIME Edm.TimeOfDay
TIMESTAMP Edm.DateTimeOffset
TINYINT Edm.Byte | Edm.SByte3
VARBINARY Edm.Binary
VARCHAR Edm.String
1 By default, long binary columns (BLOB, LONGVARBINARY) greater than 32 KB are not exposed. To expose such columns, you must take two steps. First, using the ODataBinaryColumnSizeLimit property, you must set the column size limit in a range from 32 KB to 1 MB. Then, you must expose the column, using the ODataIncludeBinaryLongData property. See Manage Limits view and Limits API for details about configuring limits.
2 By default, long character columns (LONGVARCHAR, LONGNVARCHAR, CLOB, NCLOB) greater than 32 KB are not exposed. To expose such columns, you must take two steps. First, using the ODataCharacterColumnSizeLimit property, you must set the column size limit in a range from 32 KB to 1 MB. Then, you must expose the column, using the ODataIncludeCharacterLongData property. See Manage Limits view and Limits API for details about configuring limits..
3 Value maps to EDM.Byte if described as unsigned. If the value is described as signed, it maps to EDM.SByte.