t; Filing a JIRA for this might help the next person avoid the confusion.
>
> Thanks
>
> On Sun, Jan 14, 2018 at 12:44 AM, Mikhail Sosonkin
> <mikh...@synack.com.invalid> wrote:
> > Sorry for the alarm, after some debugging, I've realized that the issue
> is
> &g
Hi,
I'm getting some strange behavior on unit tests.
(https://github.com/nologic/nifi/tree/NIFI-4731,
Hi Devs,
I'm trying to create a PR for this branch in my fork
https://github.com/nologic/nifi/tree/NIFI-4731. I see that master has moved
on to 1.5.0 but I'd like to have the processor built for 1.4 and later.
It's the version we're using. However, I don't see an origin/1.4.0 based on
the
This change seems to have fixed the problem! Thanks for pointing me in the
right direction.
Mike.
On Sat, Apr 1, 2017 at 11:01 PM, Mikhail Sosonkin <mikh...@synack.com>
wrote:
> Joe,
>
> Thanks for your response. So, I have to somehow handle all the flows that
> I ge
om/synack/nifi-gcp-pubsub-publisher/
> blob/master/src/main/java/com/synack/nifi/gcp/pubsub/
> publisher/GcpPubsubPublisher.java#L179-L181
>
> Thanks
> Joe
>
> On Fri, Mar 31, 2017 at 8:26 PM, Mikhail Sosonkin
> <mikh...@synack.com.invalid> wrote:
> > Hi All,
>
Hi All,
Wondering if someone could help me with a custom processor error. I'm
getting an error when doing a session commit in onTrigger [0].
017-03-31 23:50:44,684 ERROR [Timer-Driven Process Thread-8]
c.s.n.g.p.publisher.GcpPubsubPublisher
Hello Everyone,
SYNACK has recently started working with Google Cloud and we use NiFi to
move some of our data sets. For that, we've built processors to work with
Cloud Storage and Pubsub systems.
A processor that uploads messages to Google Cloud Platform PubSub topic:
