NIFI-15869 - PutBigQuery - Add Unknown Field Behavior property to handle fields absent from the BigQuery table schema#11171
Closed
pvillard31 wants to merge 1 commit into
Closed
NIFI-15869 - PutBigQuery - Add Unknown Field Behavior property to handle fields absent from the BigQuery table schema#11171pvillard31 wants to merge 1 commit into
pvillard31 wants to merge 1 commit into
Conversation
…dle fields absent from the BigQuery table schema
6 tasks
0BVer
pushed a commit
to 0BVer/nifi
that referenced
this pull request
Apr 24, 2026
Introduces a dedicated enum for the Unmatched Field Behavior property values, implementing DescribedValue for allowable-values integration. Cherry-picked from apache#11171 by Pierre Villard with his agreement to consolidate PRs on NIFI-15869.
Contributor
|
Consolidated into #11172 with your enum cherry-picked (authorship preserved). Thanks for the pointers! |
0BVer
added a commit
to 0BVer/nifi
that referenced
this pull request
Apr 24, 2026
Adds an 'Unmatched Field Behavior' property with three allowable values: - Ignore Unmatched Fields (default): preserves the existing behavior of silently dropping fields not present in the BigQuery table schema - Warn on Unmatched Fields: logs a warning for affected records, including the table name, count, and dotted paths of unmatched fields - Fail on Unmatched Fields: routes the FlowFile to the failure relationship Detection happens in recordToProtoMessage() before Protobuf encoding by comparing the incoming record map against the BigQuery TableSchema. The recursive traversal in collectUnmatchedFields is adapted from the approach in apache#11171 by Pierre Villard: it descends into STRUCT fields and repeated STRUCT arrays, reporting dotted field paths (e.g. parent.child.unexpected) to pinpoint schema drift in nested records. Skip Invalid Rows is intentionally decoupled from Unmatched Field Behavior. Unmatched fields signal schema drift rather than row-level validity; when FAIL mode is selected the FlowFile is always routed to failure regardless of Skip Invalid Rows. Tolerance is expressed through Ignore or Warn modes instead. The property name and behavior pattern follow PutDatabaseRecord's Unmatched Field handling approach. Co-authored-by: Pierre Villard <pierre.villard.fr@gmail.com>
Contributor
Author
|
Closing this one to work in #11172. |
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
2 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.
Summary
NIFI-15869 - PutBigQuery - Add Unknown Field Behavior property to handle fields absent from the BigQuery table schema
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking
Pull Request Tracking
NIFI-00000NIFI-00000VerifiedstatusPull Request Formatting
mainbranchVerification
Please indicate the verification steps performed prior to pull request creation.
Build
./mvnw clean install -P contrib-checkLicensing
LICENSEandNOTICEfilesDocumentation