See my response to your original post. (This looks like an accidental
double post to me)
On Wed, May 15, 2019 at 5:02 PM Jeremy Taylor <
jhtay...@everwatchsolutions.com> wrote:
> Greetings,
> https://github.com/everwatchsolutions/aces-nifi-processors-bundle
> Per the link above, there are some
Greetings,
https://github.com/everwatchsolutions/aces-nifi-processors-bundle
Per the link above, there are some custom processors that I help support.
Among those are two custom mongo processors called PartialUpdateMongo and
PutMongoWithDuplicateCheck. I’m going to list a little background
I think the problem stems from the fact that your NAR doesn't have a
dependency on the mongo api nar from our bundle. See nifi-mongodb-nar as an
example from our code base.
Thanks,
Mike
On Wed, May 15, 2019 at 4:49 PM Jeremy Taylor <
jhtay...@everwatchsolutions.com> wrote:
> Greetings,
>
Greetings,
https://github.com/everwatchsolutions/aces-nifi-processors-bundle
Per the link above, there are some custom processors that I help support.
Among those are two custom mongo processors called PartialUpdateMongo and
PutMongoWithDuplicateCheck. I’m going to list a little background
There are several complications using Snappy but from what I can tell the
SelectHiveQL Processor isn't trying to use it and instead the Hive JDBC Driver
is trying to use it. Are you running a specific vendors distribution of NiFi?
The reason I'm asking is when I go look at the source for the
