Re: Controller services visibility problem

[Panos Geo]

Hello Mark and Joe,


Thank you very much for your replies. This explains the behaviour we have been 
seeing.


The hint to look for the Operate palette instead of the top right corner made 
the difference []


Best regards,

Panos



From: Mark Payne 
Sent: Thursday, November 17, 2016 3:16 PM
To: users@nifi.apache.org
Subject: Re: Controller services visibility problem

Hi Panos,

You are correct in that Controller Services that are created in the top-right 
corner will not be available
to Processors. These are "controller-level" services and are available only to 
Reporting Tasks and other
Controller Services.

If you want to use a Controller Service for Processors, then you need to create 
the service at the Process Group
level (in the Operate palette). A Controller Service that is created here is 
available to any Processor in this group
and any child group. So if you want a Controller Service to be available to all 
Processors, you can simply create
the Controller Service at the Root Process Group, and all child groups will 
then have access to it.

Thanks
-Mark


On Nov 17, 2016, at 9:10 AM, Panos Geo 
> wrote:


Hello all,

We are using NiFi 1.0 over http without any authentication, so all our users 
are coming to NiFi as anonymous.

The problem we are having is of controller services visibility. So if we create 
a controller service (say database connection) from the top right option of the 
canvas, this is not visible within a group of processors. Also the contrary is 
also true, if we create a controller service for a group of processors, this is 
not visible to the rest of the canvas.

Is there a way to assign visibility for a controller service, e.g. set global 
visibility for a service, so that we don’t have to recreate it in all the 
groups of processors that need it?

As a side note, we didn't have this problem with NiFi versions before 1.0.

Many thanks,
Panos

Re: data flow from one s3 bucket to another

[Gop Krr]

Thanks Koji. I was able to solve this problem but what you have attached is
very useful.

On Wed, Nov 16, 2016 at 6:43 PM, Koji Kawamura 
wrote:

> Hello Gop,
>
> Have you already found how to move data around S3 buckets? I hope you do.
> But just in case if you haven't yet, I wrote a simple NiFi flow and
> shared it in Gist:
> https://gist.github.com/ijokarumawak/26ff675039e252d177b1195f3576cf9a
>
> I misconfigured region and got an error once, but after I setup bucket
> name, region and credential correctly, it worked as expected.
> I'd recommend to test a S3 related flow using ListS3 processor, to see
> if the credential can properly access the target S3 bucket.
>
> Thanks,
> Koji
>
> On Fri, Oct 28, 2016 at 7:35 AM, Gop Krr  wrote:
> > Has anyone implemented data copy from one s3 bucket to another. i would
> > greatly appreciate if you can share with me your sample processors
> > configuration.
> > Thanks
> > Rai
>

Re: Resource directory paths are malformed: docs

[Alessio Palma]

Thanks for you time, It has been resolved.
Due to a pom.xml misconfiguration the docs folder was not present.

bin
conf
docs  <--- this was missing.
lib
logs
release.version
storage -> /opt/storage
wwwdocs

I fixed the pom.xml and anything worked fine.
Mumble...  I my opinion "Folder not found" works better than "Resource 
directory paths are malformed"



From: Pierre Villard 
Sent: Thursday, November 17, 2016 6:30:15 PM
To: users@nifi.apache.org
Subject: Re: Resource directory paths are malformed: docs

Hi Alessio,

Could you copy/paste the full stack trace?

Thanks!
Pierre

2016-11-17 17:03 GMT+01:00 Alessio Palma 
>:

Hello all,

I rebuild nifi from scratch and after the deploy Jetty won't restartslogs 
returns this error:


at java.lang.reflect.Constructor.newInstance(Constructor.java:423) 
~[na:1.8.0_92]
at org.apache.nifi.NiFi.(NiFi.java:146) 
~[nifi-runtime-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at org.apache.nifi.NiFi.main(NiFi.java:243) 
~[nifi-runtime-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
Caused by: java.lang.IllegalStateException: Resource directory paths are 
malformed: docs
at 
org.apache.nifi.web.server.JettyServer.createDocsWebApp(JettyServer.java:540) 
~[nifi-jetty-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at org.apache.nifi.web.server.JettyServer.loadWars(JettyServer.java:321) 
~[nifi-jetty-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at org.apache.nifi.web.server.JettyServer.(JettyServer.java:144) 
~[nifi-jetty-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]

any idea where to look / how to fix this ?