Actually on second thought it's not negative logic, it should be checking
against tableNameFromMeta.
Sent from my iPhone
> On Mar 5, 2016, at 6:57 PM, Bryan Bende wrote:
>
> I think this a legitimate bug that was introduced in 0.5.0.
>
> I created this ticket: https://issues.apache.org/jira/
That's on me, that commit went into 0.5.0 and looks like a negative logic
error. I thought I had unit tested it but I guess not :(
Sent from my iPhone
> On Mar 5, 2016, at 6:57 PM, Bryan Bende wrote:
>
> I think this a legitimate bug that was introduced in 0.5.0.
>
> I created this ticket: h
I think this a legitimate bug that was introduced in 0.5.0.
I created this ticket: https://issues.apache.org/jira/browse/NIFI-1596
For those interested, I think the line of code causing the problem is this:
https://github.com/apache/nifi/blob/0e926074661302c65c74ddee3af183ff49642da7/nifi-nar-bun
Hello Juan,
Thanks for the response,
I deploy a NiFi 0.5.1 clean installation, and the behavior is still there.
Reading other user mail of the mailing list, it seems that there is some
incompatibility between NiFi 0.5.x and Oracle databases (maybe more).
With DB2 databases works fine.
Regards
I wonder if on the controller service DBCPConnectionPool associated to your
ExecuteSQL processor you have something that can't be found since it's
stored on your older release.
On Fri, Mar 4, 2016 at 11:12 AM, Marcelo Valle Ávila
wrote:
> Hello community,
>
> I'm starting my first steps with Ni
Hello community,
I'm starting my first steps with NiFi, and enjoining how it works!
I started with version 0.4.1 and a simple flow:
ExecuteSQL -> ConvertAvroToJSON -> PutEventHub
Reading from an Oracle database, and everything works like a charm!
Few days ago NiFi 0.5.1 has been released, and