nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Morgan, Hunter" <Hunter.Mor...@capitalone.com>
Subject flow as code and minify scaling/isolation
Date Wed, 01 Feb 2017 19:37:41 GMT
is there any internal documentation on the minifi config yaml to flow xml conversion process?
i’d really like to leverage this code to go back and forth from yaml to xml flows/templates.
one thing that i think is really missing from nifi is being able to develop and version control
flows/templates with normal editors and vcs. i know the project is talking about building
versioned flow repositories and things, but some developers want to develop flow as code,
and it would be nice to have that as an option.
any feedback on these concerns? i haven’t spent enough time diving into the minifi code
to figure out how the conversion works, but i’m working on it. if anyone can get me up to
speed, and/or point me at document that outlines it, that would be great.

another topic is using minifi to deploy horizontally scalable and isolated flows. this is
especially important as presently there is no kerberos credential isolation between flows
in clustered nifi. as far as i can tell, using minifi to deploy/scale/isolate flows is not
something that was intended, but it might be a useful alternative to the clustered model.

thanks in advance

Hunter Morgan
Data Platform Engineering
540 391 0440
Hunter.Morgan@capitalone.com

________________________________________________________

The information contained in this e-mail is confidential and/or proprietary to Capital One
and/or its affiliates and may only be used solely in performance of work or services for Capital
One. The information transmitted herewith is intended only for use by the individual or entity
to which it is addressed. If the reader of this message is not the intended recipient, you
are hereby notified that any review, retransmission, dissemination, distribution, copying
or other use of, or taking of any action in reliance upon this information is strictly prohibited.
If you have received this communication in error, please contact the sender and delete the
material from your computer.
Mime
View raw message