Nabegh, I took a quick look at the code, and it looks like that is the expected behavior. There should be a flowfile attribute "executesql.row.count" that contains the number of rows. You could always route on that attribute to handle those empty result sets differently than ones that have one or more rows of data in the resulting avro file.
On Fri, Aug 5, 2016 at 3:52 PM Nabegh <[email protected]> wrote: > When no records are returned from the SQL statement, ExecuteSQL returns an > avro file that contains the schema with no data. Is this the expected > behaviour? > > Thanks. > > > > -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/ExecuteSQL-returns-empty-avro-file-tp12965.html > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. >
