fix: force attachment to use EmptyFieldAs::FieldDefault. #14767
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/
Summary
CSV attachment is mainly used in Drivers for insert.
In the future, client should use EmptyFieldAs=STRING or FieldDefault to distinguish NULL and empty string.
However, old servers ds not support
missing_field_as
, so client can not add the option directly at now.So we will get empty_field_as = NULL, which will raise error if there is empty string for non-nullable string field.
remove this after
related pr #14335
Tests
Type of change
This change is