[ 
https://issues.apache.org/jira/browse/NIFI-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648097#comment-15648097
 ] 

ASF GitHub Bot commented on NIFI-2998:
--------------------------------------

GitHub user mattyb149 opened a pull request:

    https://github.com/apache/nifi/pull/1187

    NIFI-2998: Add validator to Avro Record Name in InferAvroSchema

    
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mattyb149/nifi NIFI-2998

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1187.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1187
    
----
commit 2fecdf25770786135e673739e359ecdcaceeb7db
Author: Matt Burgess <[email protected]>
Date:   2016-11-08T16:56:14Z

    NIFI-2998: Add validator to Avro Record Name in InferAvroSchema

----


> Add validator to Avro Record Name in InferAvroSchema
> ----------------------------------------------------
>
>                 Key: NIFI-2998
>                 URL: https://issues.apache.org/jira/browse/NIFI-2998
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>              Labels: avro, beginner, beginners, easyfix, starter
>
> The Avro Record Name property in the InferAvroSchema processor is required to 
> be non-empty, but no checking is done to ensure the record name is valid for 
> Avro.
> Avro naming rules: https://avro.apache.org/docs/1.7.7/spec.html#Names
> The validator should accept the name if Expression Language is used (noting 
> in the documentation for the property that the value of the expression must 
> adhere to the Avro naming rules), or validate the property value against the 
> Avro naming rules if Expression Language is not present.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to