nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Bende <>
Subject Re: Variable / Nifi-EL for RPG Endpoint?
Date Thu, 06 Sep 2018 20:21:33 GMT
Sorry Jon, I made the assumption that you were talking about saving a
flow to NiFi Registry from say you dev environment and then importing
into another environment and figuring out how to deal with the RPG

The process I described is how RPG URLs are handled with versioned
flows in NiFi Registry, but if you are taking a different approach
based around templates, or some other mechanism, then you are correct
that the target URL doesn't currently support EL.

Traditionally EL is primarily for property descriptors which are the
fields on the properties tab of processors, controller services, and
reporting tasks. So RPG URLs kind of fall outside of that, not to say
it can't ever be supported, but I haven't thought through all the
ramifications of what that mean internally in the framework.

On Thu, Sep 6, 2018 at 4:11 PM, Andy LoPresto <> wrote:
> I think Bryan was referring to Apache NiFi Registry [1] which is the
> complementary standalone application which hosts version controlled flow
> snippets.
> [1]
> Andy LoPresto
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> On Sep 6, 2018, at 1:09 PM, Jon Logan <> wrote:
> Thanks Bryan -- Is that in terms of Docker Registry? We don't currently use
> Docker Registry, but our plan was to bundle a flow.gz into a Docker image
> directly. I'm not sure if maybe we're approaching this problem in a weird
> way? How do most people handle multiple instances in different environments
> that are disconnected from one another? We considered running a Docker
> Registry container as an option, or specifying the flow.gz directly as an
> option...both seem to have some issues and inconveniences.
> Thanks!
> Jon
> On Thu, Sep 6, 2018 at 4:01 PM, Bryan Bende <> wrote:
> Jon,
> The RPG URL is treated similar to sensitive properties or parent
> controller services, meaning that after deploying your flow you can
> issue an update to the RPG to set the URL to given environment's value
> and that change will not be considered a change as far as version
> control and will be retained when upgrading the process group to newer
> versions.
> Thanks,
> Bryan
> On Thu, Sep 6, 2018 at 3:48 PM, Jon Logan <> wrote:
> We are running into a slight issue when we wish to migrate between NiFi
> cluster instances...the RPG endpoint in our flow seems to disallow
> setting
> of a variable, which makes our flow have to be specific to the specific
> environment it's being deployed in. It seems odd that it won't let us use
> an expression there and set the value to a variable -- is this an
> oversight? Is there some design decision here that we're missing?
> Thanks!

View raw message