Either way. You can just use "docker cp" to copy the file out of a running
instance.
On Wed, Apr 8, 2020 at 12:36 PM Kevin Telford
wrote:
> Thank you Mike. This makes sense.
>
> How do you get the flow.xml.gz file? Do you have NiFi installed locally on
> bare metal or do you develop also in a
Hi,
Why not use NiFi Registry to deploy / version the flows?
Best regards,
Endre
Sent from ProtonMail mobile
Original Message
On Apr 8, 2020, 4:27 PM, Kevin Telford wrote:
> Hi all – I have a two part question.
>
> I’d like to run NiFi inside a container in order to deploy to
No, that is what I mean, I would guess that you could spin up _n_ number
of nifi nodes with registry parameters that tell it what to load etc so you
wouldn’t have to manage the flow on disk
On April 8, 2020 at 14:21:52, Chris Sampson (
chris.samp...@naimuri.com.invalid) wrote:
If you mean
If you mean having a way of telling a new nifi instance about a registry,
bucket and flow to load at startup, then I'd say yes that would be good. Or
even to be able to directly import the flow json that can currently be
exported from registry (or nifi).
Is this effectively what NiFi serverless
The ConsumeEWS processor has no special handling for multipart mime
messages. It would need to be extended to have more control over the
output. It looks like all you can do is specify headers to include or
ignore.
On April 8, 2020 at 13:02:21, Jisson Dennis (jissonden...@gmail.com) wrote:
Hi
Can I ask a silly question? Would the ability for nodes to load flows
from the registry make this easier? Would that even make sense?
On April 8, 2020 at 12:52:19, Chris Sampson (
chris.samp...@naimuri.com.invalid) wrote:
When first starting with NiFi (I've always used it in container form),
Hi ,
I have a usecase to monitor an exchange mailbox.
Using ConsumeEWS I am able to bind the inbox and receive the email flow
file. However, the message body alone cannot be extracted by the custom
processors next to ConsumeEWS.
All the mime parts including the attachment are parsed into a single
When first starting with NiFi (I've always used it in container form), I
looked at taking a similar approach with the flow.xml.gz, but quickly moved
away from that after reading various tales online about it not always being
very portable and/or people having issues keeping it in sync (remembering
Thank you Mike. This makes sense.
How do you get the flow.xml.gz file? Do you have NiFi installed locally on bare
metal or do you develop also in a container? Initially I was thinking of adding
a custom volume to facilitate both getting and deploying the flow file.
Best,
Kevin
On 2020/04/08
Michal,
Should be fixed, could you confirm?
May not all mirrors are synced, give it some time in case you still see the
old contents.
Thanks for letting us know!
Cheers,
Arpad
On Wed, Apr 8, 2020 at 10:55 AM Arpad Boda wrote:
> Michal,
>
> Most probably you are right, will check and get
The NiFi Registry is another option to deploy versioned flows in a running
NiFi container.
It would require to deploy the container, and make some API calls to deploy
the flow.
Pierre
Le mer. 8 avr. 2020 à 16:38, Mike Thomsen a écrit :
> What I've done in the past looks something like this:
>
What I've done in the past looks something like this:
FROM apache/nifi:1.11.4
COPY flow.xml.gz /opt/nifi/nifi-current/conf/flow.xml.gz
And that's it. The obvious caveat is that you need to follow good practices
with ensuring that your flow and the way you setup the container can
replicate the
Hi all – I have a two part question.
I’d like to run NiFi inside a container in order to deploy to various
environments. As far as I can tell, the flow.xml.gz file is the main
“source” if you will, for a NiFi data flow.
Q1) Is the flow.xml.gz file the “source” of a NiFi data flow, and if so,
Michal,
Most probably you are right, will check and get back to you.
On Wed, Apr 8, 2020 at 10:47 AM Michal Klempa
wrote:
> Hi all,
> the 'format' of sha256 file has changed (although it is still a valid
> sha256 output). Haven't you experienced problems with Docker image build
> with this?
>
Hi all,
the 'format' of sha256 file has changed (although it is still a valid
sha256 output). Haven't you experienced problems with Docker image build
with this?
See the change:
$ curl
https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.6.0/nifi-registry-0.6.0-bin.tar.gz.sha256
15 matches
Mail list logo
