Sign inTry Free

Debezium Data Type Mapping

On this page

Each change event record is structured similar to the original table, where the event record includes a field for each column value. The data type of a table column determines how the connector represents the column’s values in the change event fields.

For each table column, Debezium maps the source data type to a literal type, and in some cases, to a semantic type in the corresponding event field.

  • Literal types: Specify how the value is literally represented, using one of the following Kafka Connect schema types: INT8, INT16, INT32, INT64, FLOAT32, FLOAT64, BOOLEAN, STRING, BYTES, ARRAY, MAP, and STRUCT.

  • Semantic types: Specify how Kafka Connect schema captures the meaning of the field, by using the name of the Kafka Connect schema for the field.

Integer Numbers

SingleStore Data Type

Literal type

BOOL

INT16

BIT

BYTES

TINYINT

INT16

SMALLINT

INT16

MEDIUMINT

INT32

INT

INT32

BIGINT

INT64

Real Numbers

SingleStore Data Type

Literal type

FLOAT

FLOAT32

DOUBLE

FLOAT64

The connector handles DECIMAL values based on the value of the decimal.handling.mode connector configuration property.

decimal.handling.mode

Literal type

Semantic type

precise (default)

BYTES

org.apache.kafka.connect.data.Decimal: Contains an integer that specifies the number of places the decimal point is shifted.

double

FLOAT64

N/A

string

STRING

N/A

Time and Date

The connector handles time and date types based on the value of the time.precision.mode connector configuration property.

time.precision.mode = adaptive_time_microseconds (Default)

SingleStore Data Type

Literal type

Semantic type

DATE

INT32

io.debezium.time.Date: Represents the number of days since the epoch.

TIME

INT64

io.debezium.time.MicroTime: Represents the time value in microseconds.

TIME(6)

INT64

io.debezium.time.MicroTime: Represents the time value in microseconds.

DATETIME

INT64

io.debezium.time.Timestamp: Represents the number of milliseconds past the epoch.

DATETIME(6)

INT64

io.debezium.time.MicroTimestamp: Represents the number of microseconds past the epoch.

TIMESTAMP

INT64

io.debezium.time.Timestamp: Represents the number of milliseconds past the epoch.

TIMESTAMP(6)

INT64

io.debezium.time.MicroTimestamp: Represents the number of microseconds past the epoch.

YEAR

INT32

N/A

time.precision.mode = connect

SingleStore Data Type

Literal type

Semantic type

DATE

INT32

org.apache.kafka.connect.data.Date: Represents the number of days since the epoch.

TIME

INT64

org.apache.kafka.connect.data.Time: Represents the time value in milliseconds.

TIME(6)

INT64

org.apache.kafka.connect.data.Time: Represents the time value in milliseconds.

DATETIME

INT64

org.apache.kafka.connect.data.Timestamp: Represents the number of milliseconds since the epoch.

DATETIME(6)

INT64

org.apache.kafka.connect.data.Timestamp: Represents the number of milliseconds since the epoch.

TIMESTAMP

INT64

org.apache.kafka.connect.data.Timestamp: Represents the number of milliseconds since the epoch.

TIMESTAMP(6)

INT64

org.apache.kafka.connect.data.Timestamp: Represents the number of milliseconds since the epoch.

YEAR

INT32

N/A

time.precision.mode = adaptive

SingleStore Data Type

Literal type

Semantic type

DATE

INT32

io.debezium.time.Date: Represents the number of days since the epoch.

TIME

INT64

io.debezium.time.Time: Represents the time value in milliseconds.

TIME(6)

INT64

io.debezium.time.MicroTime: Represents the time value in microseconds.

DATETIME

INT64

io.debezium.time.Timestamp: Represents the number of milliseconds past the epoch.

DATETIME(6)

INT64

io.debezium.time.MicroTimestamp: Represents the number of microseconds past the epoch.

TIMESTAMP

INT64

io.debezium.time.Timestamp: Represents the number of milliseconds past the epoch.

TIMESTAMP(6)

INT64

io.debezium.time.MicroTimestamp: Represents the number of microseconds past the epoch.

YEAR

INT32

N/A

String Types

SingleStore Data Type

Literal type

TINYTEXT

STRING

TEXT

STRING

MEDIUMTEXT

STRING

LONGTEXT

STRING

CHAR

STRING

VARCHAR

STRING

Blob Types

The connector handles binary data types based on the value of the binary.handling.mode connector configuration property.

SingleStore Data Type

Literal type

Semantic type

TINYBLOB

BYTES or STRING

Represents as either the raw bytes (the default), a base64-encoded String, a base64-url-safe-encoded String, or a hex-encoded String, based on binary.handling.mode connector configuration property.

BLOB

BYTES or STRING

Represents as either the raw bytes (the default), a base64-encoded String, a base64-url-safe-encoded String, or a hex-encoded String, based on the binary.handling.mode connector configuration property.

MEDIUMBLOB

BYTES or STRING

Represents as either the raw bytes (the default), a base64-encoded String, a base64-url-safe-encoded String, or a hex-encoded String, based on the binary.handling.mode connector configuration property.

LONGBLOB

BYTES or STRING

Represents as either the raw bytes (the default), a base64-encoded String, a base64-url-safe-encoded String, or a hex-encoded String, based on the binary.handling.mode connector configuration property.

BINARY

BYTES or STRING

Represents as either the raw bytes (the default), a base64-encoded String, a base64-url-safe-encoded String, or a hex-encoded String, based on the binary.handling.mode connector configuration property.

VARBINARY

BYTES or STRING

Represents as either the raw bytes (the default), a base64-encoded String, a base64-url-safe-encoded String, or a hex-encoded String, based on the binary.handling.mode connector configuration property.

BSON

BYTES or STRING

Represents as either the raw bytes (the default), a base64-encoded String, a base64-url-safe-encoded String, or a hex-encoded String, based on the binary.handling.mode connector configuration property.

Geospatial Types

The connector handles geospatial types based on the value of the geography.handling.mode connector configuration property.

geography.handling.mode = geometry (Default)

SingleStore Data Type

Literal type

Semantic type

GEOGRAPHYPOINT

STRUCT

io.debezium.data.geometry.Geometry: Contains a structure with two fields:

  • srid (INT32): Spatial reference system ID that defines the type of geometry object stored in the structure.

  • wkb (BYTES): Binary representation of the geometry object encoded in the Well-Known-Binary (wkb) format.

Refer to the Open Geospatial Consortium for more details.

GEOGRAPHY

STRUCT

io.debezium.data.geometry.Geometry: Contains a structure with two fields:

  • srid (INT32): Spatial reference system ID that defines the type of geometry object stored in the structure.

  • wkb (BYTES): Binary representation of the geometry object encoded in the Well-Known-Binary (wkb) format.

Refer to the Open Geospatial Consortium for more details.

geography.handling.mode= string

SingleStore Data Type

Literal type

GEOGRAPHYPOINT

STRING

GEOGRAPHY

STRING

Vector Types

The connector handles geospatial types based on the value of the vector.handling.mode connector configuration property.

vector.handling.mode = string (Default)

SingleStore Data Type

Literal type

VECTOR

STRING

vector.handling.mode = binary

SingleStore Data Type

Literal type

Semantic Type

VECTOR

BYTES or STRING

Represents as either the raw bytes (the default), a base64-encoded String, a base64-url-safe-encoded String, or a hex-encoded String, based on the binary.handling.mode connector configuration property.

vector.handling.mode = array

SingleStore Data Type

Literal type

VECTOR

ARRAY

Other Types

SingleStore Data Type

Literal type

JSON

STRING

ENUM

STRING

SET

STRING

Last modified: April 1, 2025

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK