You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an input schema has columns that map to Java primitive types (short, int, long), and JDBC Native is on, the resulting data contains default values (0) instead of nulls for nullable columns.
Code and/or configuration snippet that caused the issue
Describe the bug
When an input schema has columns that map to Java primitive types (short, int, long), and JDBC Native is on, the resulting data contains default values (0) instead of nulls for nullable columns.
Code and/or configuration snippet that caused the issue
Expected behavior
Nullable fields should retain 'null' value when loaded via JDBC Native.
Context
The text was updated successfully, but these errors were encountered: