tolerate null transformation attrs in ColumnLineageInputField #2600
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.
Problem
The
transformationType
andtransformationDescription
attributes for column-level lineage are optional at the database level and can be safely omitted when pushing in lineage events.However, because they're marked as non-nullable in the Java client's representation, an exception is thrown when deserialising a response from the column lineage endpoint (thanks to Lombok-generated
Objects.requireNonNull
in the constructor).Solution
Remove the
@NonNull
annotation from the client class and the@NotNull
from the model class. Add a test that would fail without this change. Validated by running the stack locally.One-line summary:
tolerate null transformation attrs in field model
Checklist
CHANGELOG.md
(Depending on the change, this may not be necessary)..sql
database schema migration according to Flyway's naming convention (if relevant)