https://community.cloudera.com/t5/Support-Questions/NiFi-Applying-an-Avro-Schema-in-ConvertCSVToAvro/m-p/148547#M111073 <P>EDIT: I noticed that my REAL record schema was occasionally using integers as the name, and that violated the field name requirements for avro. So, the schema worked once I added a character before the integers.</P><P>With NiFi's ConvertCSVToAvro, I have not found much guidance or example regarding the Record Schema Property. The documentation says to use an Avro schema, and it seems like a canonical Avro schema does not work. <STRONG>How do I set it up??</STRONG></P><P>My efforts resulted in the caution symbol saying the message below, and the inability to actually use the processor.</P><P>'Record schema' validated against '&lt;text of record schema&gt;'</P><P>Here are the properties as I set them...</P><P>Record schema:</P><PRE>{ "type": "record", "name": "sensor_data", "fields": [ { "name": "TimeStamp", "type": "string"}, { "name": "Sensor", "type": "string"}, { "name": "Measure", "type": "string"}, { "name": "MeasureValue", "type": ["int","null"], "default":"null"}, { "name": "AdditionalInfo", "type": ["string","null"], "default":"null"} ] }</PRE><P>CSV charset: utf8</P><P>CSV delimiter: |</P><P>CSV quote character: "</P><P>CSV escape character: \</P><P>Use CSV header line: false</P><P>Lines to skip: 0</P><P>Here's some sample data:</P><PRE>2016-02-01T00:03:09Z|Temp_1|TempF|212|"WARNING|Overheating" 2016-02-01T00:05:03Z|Power|N/A||"STATE_CHANGE|Active" 2016-02-02T12:30:00Z|EmployeeCount|0|</PRE> Fri, 19 Feb 2016 01:01:37 GMT scardella 2016-02-19T01:01:37Z