[
https://issues.apache.org/jira/browse/NIFI-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096270#comment-16096270
]
ASF GitHub Bot commented on NIFI-4142:
--------------------------------------
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2015#discussion_r128764060
--- Diff:
nifi-commons/nifi-record/src/main/java/org/apache/nifi/serialization/SchemaValidationException.java
---
@@ -15,14 +15,16 @@
* limitations under the License.
*/
-package org.apache.nifi.serialization.record;
+package org.apache.nifi.serialization;
-public class TypeMismatchException extends RuntimeException {
--- End diff --
I don't agree that they are pretty much the same thing.
TypeMismatchException is very specific. SchemaValidationException can be much
more broad. For instance, if a required field is missing, that is not a Type
Mismatch, but it is a Schema Validation.
> Implement a ValidateRecord Processor
> ------------------------------------
>
> Key: NIFI-4142
> URL: https://issues.apache.org/jira/browse/NIFI-4142
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 1.4.0
>
>
> We need a processor that is capable of validating that all Records in a
> FlowFile adhere to the proper schema.
> The Processor should be configured with a Record Reader and should route each
> record to either 'valid' or 'invalid' based on whether or not the record
> adheres to the reader's schema. A record would be invalid in any of the
> following cases:
> - Missing field that is required according to the schema
> - Extra field that is not present in schema (it should be configurable
> whether or not this is a failure)
> - Field requires coercion and strict type checking enabled (this should also
> be configurable)
> - Field is invalid, such as the value "hello" when it should be an integer
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
