at I’m looking at doing. I
> need a way for a custom Record Reader to pass information downstream on parse
> failures so that they can be logged for futhur investigation by a human. I’d
> like to have AbstractRecordProcessor add an attribute record.error.message on
> the flow file
I’d like to get some feedback on an enhancement that I’m looking at doing. I
need a way for a custom Record Reader to pass information downstream on parse
failures so that they can be logged for futhur investigation by a human. I’d
like to have AbstractRecordProcessor add an attribute
Excellent, thanks for the feedback guys!
Regards,Chris
Original message From: Joe Witt <joe.w...@gmail.com> Date:
6/17/17 10:20 AM (GMT-06:00) To: dev@nifi.apache.org Subject: Re:
AbstractRecordProcessor
+1 to bryans comments
On Sat, Jun 17, 2017 at 8:18 AM, Bryan
s is my second attempt for some reason my email client likes to defer
>> to my non-registered email to write to the list, (I doubt it happened but
>> if you receive this twice, many apologies).
>>
>> I was starting to work on the HBase record processors, and while lookin
to work on the HBase record processors, and while looking
> around found the AbstractRecordProcessor in
> org.apache.nifi.processors.standard. Best I can tell, this is currently
> implemented in UpdateRecord and ConvertRecord. However,
> AbstractRecordProcessor extends AbstractProces
Hi All,
I was starting to work on the HBase record processors, and while looking around
found the AbstractRecordProcessor in org.apache.nifi.processors.standard. Best
I can tell, this is currently implemented in UpdateRecord and ConvertRecord.
However, AbstractRecordProcessor extends
the AbstractRecordProcessor in org.apache.nifi.processors.standard. Best
I can tell, this is currently implemented in UpdateRecord and ConvertRecord.
However, AbstractRecordProcessor extends AbstractProcessor with the addition
record-specific logic, thus making it a slightly better starting point from
