Fix testTableWithNonNullableColumns to update NOT NULL column in Delta Lake connector#16883
Merged
ebyhr merged 1 commit intotrinodb:masterfrom Apr 5, 2023
Merged
Fix testTableWithNonNullableColumns to update NOT NULL column in Delta Lake connector#16883ebyhr merged 1 commit intotrinodb:masterfrom
testTableWithNonNullableColumns to update NOT NULL column in Delta Lake connector#16883ebyhr merged 1 commit intotrinodb:masterfrom
Conversation
ebyhr
force-pushed
the
ebi/delta-fix-test
branch
from
40f47aa to
237b6b6
Compare
krvikash
approved these changes
Apr 5, 2023
homar
approved these changes
Apr 5, 2023
findepi
approved these changes
Apr 5, 2023
findepi
added
test
no-release-notes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Description
Fix
testTableWithNonNullableColumnsto update NOT NULL column in Delta Lake connector.The
col2is nullable column, so those UPDATE statement shouldn't fail in my understanding.I guess it's a typo of the column name.
Release notes
(x) This is not user-visible or docs only and no release notes are required.