glad you found how to get through it - we should make the user experience
better. What led you to find the solution?
On Thu, Mar 14, 2019 at 4:33 PM Mikhail Rolshud (BLOOMBERG/ 120 PARK) <
mrols...@bloomberg.net> wrote:
> Ignore this - it had nothing to do with registry or versions.
>
> Looks like I was just missing "view the component" permission on main
> canvas for the account that we use to deploy the flows.
>
> From: users@nifi.apache.org At: 03/14/19 16:09:02
> To: users@nifi.apache.org
> Subject: Registry 1.8.0 flows fail to import into 1.9.1 node
>
> Hi guys.
>
> I developed some flows on nifi 1.8.0 and committed them to nifi registry.
> Now I am trying to deploy them to the nifi node that runs nifi 1.9.1 using
> nifi cli.sh from toolkit.
>
> cli.sh nifi pg-import -b "4ffb0e6f-dc5d-4546-b11d-694bcca2f89b" -f
> "802aab58-32a3-457f-bfdd-f927699944b7" -fv 37
>
> I got "ERROR: Error executing command 'pg-import' : Error creating process
> group: An unexpected error has occurred. Please check the logs for
> additional details."
> bucket id and flow id and version are valid and same import works fine for
> 1.8.0 node.
> There is nothing in nifi-app.log.
>
> I did notice that in the .snapshot file in github for the flow I am trying
> to import - below block exists for most of the parts of my flow where
> artifact version is saved as 1.8.0.
>
> "bundle" : {
> "artifact" : "nifi-standard-nar",
> "group" : "org.apache.nifi",
> "version" : "1.8.0"
> },
>
>
> Is there a way to make pg-import ignore this?
> What is the recommended way to import 1.8.0 flows from nifi registry to
> 1.9.1 node?
>
> Thank you
>
>
>
