0BVer opened a new pull request, #11172: URL: https://github.com/apache/nifi/pull/11172
<!-- Licensed to the Apache Software Foundation (ASF) under one or more --> <!-- contributor license agreements. See the NOTICE file distributed with --> <!-- this work for additional information regarding copyright ownership. --> <!-- The ASF licenses this file to You under the Apache License, Version 2.0 --> <!-- (the "License"); you may not use this file except in compliance with --> <!-- the License. You may obtain a copy of the License at --> <!-- http://www.apache.org/licenses/LICENSE-2.0 --> <!-- Unless required by applicable law or agreed to in writing, software --> <!-- distributed under the License is distributed on an "AS IS" BASIS, --> <!-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. --> <!-- See the License for the specific language governing permissions and --> <!-- limitations under the License. --> # Summary [NIFI-15869](https://issues.apache.org/jira/browse/NIFI-15869) Adds a new `Unmatched Field Behavior` property to `PutBigQuery` with the following allowable values: - `Ignore Unmatched Fields` (default): preserves the current behavior and silently ignores fields not present in the BigQuery table schema - `Warn on Unmatched Fields`: ignores unmatched fields but logs a warning for each affected record - `Fail on Unmatched Fields`: treats unmatched fields as an error and routes the FlowFile to the failure relationship In NiFi 2.x, `PutBigQuery` can silently drop record fields that are absent from the destination BigQuery table schema during Protobuf encoding in `ProtoUtils.createMessage()`. This can lead to undetected data loss in CDC pipelines when source-side columns are added without corresponding BigQuery schema updates. This change detects unmatched fields earlier in `recordToProtoMessage()` by comparing the incoming record map against the BigQuery table schema before Protobuf encoding. The property name and behavior pattern follow the existing unmatched field / column handling approach used in processors such as `PutDatabaseRecord`. Also added tests covering: - warning behavior for unmatched fields - failure routing when unmatched fields are configured to fail - interaction with `Skip Invalid Rows=true`, where invalid records are skipped and the FlowFile can still succeed # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-00000` - Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-00000` - Pull request contains [commits signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) with a registered key indicating `Verified` status ### Pull Request Formatting - Pull Request based on current revision of the `main` branch - Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `./mvnw clean install -P contrib-check` - [ ] JDK 21 - [ ] JDK 25 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
