Hi Koji,
Thank you for testing my problem with NiFi 1.4 and verifying that it works. It is good to know that once we upgrade our NiFi infrastructure, the problem would go away.


On Tuesday, November 7, 2017, 1:14:11 AM MST, Koji Kawamura <ijokarumawak@gmail.com> wrote:

Hi Pradip,

When I tested the scenario with NiFi 1.4, SplitAvro created an
outgoing FlowFile containing single record as expected when the
incoming FlowFile only has one Avro record.

In SplitAvro change histories, I found NIFI-2841. I assume the change
fixed the split behavior with single input record as well.
Upgrading to newer NiFi is recommended. NIFI-2841 is fixed in NiFi 1.1.


On Fri, Nov 3, 2017 at 2:37 AM, Pradip <kpradip@yahoo.com> wrote:
> I have a NiFi flow that queries a relational Table that has a latestUpdate
> date timestamp column  and forwards data in that table that was
> inserted/modified in the last 10 min sends it to a JMS queue. The flow is
> something like this
> ExecuteSQL --> splitAvro --> convertAvroToJson --> some more processing -->
> publishJMS
> The problem I am running into is if the ExecuteSQL returns a single row of
> data, the splitAvro doesn't forward the single row of data on the split
> downstream.
> The splitAvro has the following properties set:
> Split Stratergy:  Record
> Output Size:  1
> Output Strategy: Datafile
> Transfer Metadata: true
> Is this a bug in the splitAvro code, because I would expect the data to get
> split if there is 1 or more records in the flowfile?
> I am running on NiFi 1.0
> Thanks,
> Pradip