Last updated on Apr 25, 2024

Hevo supports the following variations of MySQL as a Source:

Refer to the required MySQL variant for the steps to configure it as a Source in your Hevo Pipeline and start ingesting data.

Handling the Unsigned Data Type

While converting the data types of the ingested data prior to replication to the Destination, some values may be truncated if they exceed the allowed limit, or the Event might fail if the value mismatches with the schema. This can happen in the MySQL database with the unsigned int type since it can hold more positive values than the signed int. For example, the 8-bit unsigned int holds 256 values, from 0 to 255, while the 8-bit signed int also holds 256 values but they range from -127 to 127. Thus, the positive range of the unsigned int (0-255) will be greater than the positive range of the signed int (0-127).

Hence, to avoid data loss, Hevo automatically updates the unsigned int to a larger signed int type. For example, an 8-bit unsigned int is promoted to a 16-bit signed int as it has more space to store the value.

See Also

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Apr-29-2024 NA Removed sections, Select the Source Type and Specify MySQL Connection Settings.
Mar-05-2024 NA Updated links.
Nov-03-2023 NA Removed section, Object Settings.
Apr-21-2022 1.86 - Updated section, Object Settings.
- Removed section, Select the Pipeline Mode.
Dec-06-2021 1.77 Added the section, Handling the Unsigned Data Type.
Jul-12-2021 1.67 - Added the field Include new tables in the Pipeline under Source configuration settings.
- Moved the steps for configuring the Source from the Specify MySQL Connection Settings section to the respective MySQL variant document.
Mar-09-2021 1.58 Updated section Select the Pipeline Mode to include Change Tracking as a Pipeline mode.

Tell us what went wrong