UNEXPECTED VALUE ERROR (INTEGER, FLOAT)
“: expected integer value, but unexpected value ‘1.333334’ given”
Explanation:
This error occurs when a field in the source is set to an incorrect data type. In the example above, the schema is expecting an integer, but a float value (e.g., ‘1.333334’) was provided. However, the error message typically does not specify which column is causing the problem. As a result, you’ll need to manually test different columns to identify the one that’s incorrectly configured.
How to Fix:
-
Identify the potential problematic column(s):
Since the error message doesn’t usually indicate which column is problematic, you’ll need to investigate by reviewing the source and identifying fields that could potentially cause the issue (e.g., fields that are expected to be integers but might contain float values). -
Track tested columns:
As you make changes, it’s important to track which columns you have tested to ensure you preserve the original settings for those that aren’t causing the error. This will help you systematically narrow down the problematic column without losing track of your progress. -
Update the schema:
Once you suspect a column, change its data type (e.g., from float to integer) in the source’s schema section (as per screenshoot).
- Manually run the source:
After making the change, manually run the source to check if the error persists. If the error is still present, move on to test the next column. - Test and confirm:
Continue adjusting the data types of the columns until the source runs successfully. Once the correct column is fixed, the source will return to an active status.
By following these steps, you can identify and correct the issue while ensuring the integrity of the original schema settings.