Re: difficulty killing NiFi w/ nifi.sh stop under 1.2.0 now vs. 1.1.2 when run as systemd service

[Andre]

Jeremy,

I am not familiar with Bitbucket pipelines but would you mind explaining
why are you wrapping the deployment with sudo?

Reason I ask is because nifi.sh already has logic to drop the process
privileges from root to an uid of choice.

Cheers

On Sat, May 27, 2017 at 1:33 AM, Jeremy Taylor 
wrote:

> Greetings,
>
> I’m hoping to upgrade the my software team’s baseline to use NiFi 1.2.0.
> I’m having trouble w/ a particular situation of trying to take nifi down.
> Prior to this version, I’ve been able to use the nifi.sh script w/o sudo
> rights to kill nifi when it has been brought up by a service (systemd, not
> init.d).
>
> Main points:
>
> 1) We have had auto-deploy working via bitbucket pipelines to a staging
> system that has auto deployed all the nifi required files from our baseline
> (not nifi internal configs).
>
> 2) The AWS VM that runs nifi autmatically starts up nifi in a service
> state via systemd services.  We masquerade running it as a non-root user w/
> sudo rights, but do not use those sudo rights as scripts in bitbucket
> pipelines won’t support sudo rights.
>
> 3) The deploy script for our staging server that runs nifi attempts to
> take down nifi with a `nifi.sh stop`, which has worked prior to this
> version.  The newer nifi flow being deployed is manipulated via XSL and
> then copied in where it needs to go before restarting nifi w/ `nifi.sh
> start` ; (we stop using systemd upon the first deploy to the staging system)
>
> 4) I’ve done a diff between the latest nifi.sh and the previous nifi.sh
> from 1.1.2 and only see a tiny difference.
>
> 5) Our staging server starts up every morning and brings up nifi and
> related services via systemd services.
>
> 6) I realize using nifi as an init.d service is more supported than using
> it as a systemd service.  However, we’ve not been able to masquerade as a
> different user properly very well when using init.d.  Having to be root for
> bitbucket pipelines would also be a dealbreaker for us.  Thus, having the
> service being run as a user other than root is important to us.
>
> 7) For reference, our systemd service file only deals with calling the
> RunNiFi class and does not bother with the nifi shell script.
>
>
>
> Questions:
> 1) Would anyone know why a simple “nifi.sh stop” would no longer kill a
> pre-existing nifi process being run as a systemd service in nifi 1.2.0?
>
> 2) We are thinking of attempting a brute force kill that would kill the
> “RunNiFi start” Java process.  We are concerned that not exiting gracefully
> would be really bad for nifi and related nifi repositories.  Would this
> route be recommended anyway in our circumstance?
> 3) Any further recommendations?
>
>
>
> --Jeremy
>

RE: Nifi Authentication

[Shrey Kapoor]

Thanks a lot Matt.

From: Matt Gilman [mailto:matt.c.gil...@gmail.com]
Sent: Friday, May 26, 2017 12:00 PM
To: users@nifi.apache.org
Subject: Re: Nifi Authentication

No worries. Check the download page that I linked to. The nifi-toolkit is 
separate. The downloads page contains the toolkit for 1.2.0. I just double 
checked and it looks like support for encrypted configs was introduce in 1.1.0 
so you should be good.

Thanks

Matt

On Fri, May 26, 2017 at 2:55 PM, Shrey Kapoor 
mailto:shrey.kap...@ds-iq.com>> wrote:
Hi Matt,

I have nifi-1.1.1-bin.tar.gz installed. But I do not find encrypt-config tool 
in my bin directory. Is encrypt-config tool a part of nifi-toolkit only or Is 
it not a part version 1.1.1 ? Apologies for my ignorance. I am now to nifi.

Regards,
Shrey

From: Matt Gilman 
[mailto:matt.c.gil...@gmail.com]
Sent: Friday, May 26, 2017 11:38 AM
To: users@nifi.apache.org
Subject: Re: Nifi Authentication

Shrey,

1) I believe that you can use the encrypt-config tool that is part of the 
nifi-toolkit to encrypt the sensitive parts of the login-identity-providers.xml 
file. The documentation for that is available in the admin guide [1]. The 
nifi-toolkit is available on the downloads page [2].

2) NiFi does not support AD groups yet. There is work currently underway that 
will facilitate groups being loaded from an external source.

Thanks

Matt

[1] 
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#encrypted-passwords-in-configuration-files
[2] https://nifi.apache.org/download.html

On Fri, May 26, 2017 at 2:15 PM, Shrey Kapoor 
mailto:shrey.kap...@ds-iq.com>> wrote:

Hi,



I have a couple of questions.

1. Is it possible to NOT put the Manager Password, Truststore Password and 
Keystore password in clear text in login-identity-providers.xml file?

2. Does Nifi support adding AD groups yet?



Regards,

Shrey

Re: Nifi Authentication

[Matt Gilman]

No worries. Check the download page that I linked to. The nifi-toolkit is
separate. The downloads page contains the toolkit for 1.2.0. I just double
checked and it looks like support for encrypted configs was introduce in
1.1.0 so you should be good.

Thanks

Matt

On Fri, May 26, 2017 at 2:55 PM, Shrey Kapoor 
wrote:

> Hi Matt,
>
>
>
> I have nifi-1.1.1-bin.tar.gz installed. But I do not find encrypt-config
> tool in my bin directory. Is encrypt-config tool a part of nifi-toolkit
> only or Is it not a part version 1.1.1 ? Apologies for my ignorance. I am
> now to nifi.
>
>
>
> Regards,
>
> Shrey
>
>
>
> *From:* Matt Gilman [mailto:matt.c.gil...@gmail.com]
> *Sent:* Friday, May 26, 2017 11:38 AM
> *To:* users@nifi.apache.org
> *Subject:* Re: Nifi Authentication
>
>
>
> Shrey,
>
>
>
> 1) I believe that you can use the encrypt-config tool that is part of the
> nifi-toolkit to encrypt the sensitive parts of the
> login-identity-providers.xml file. The documentation for that is
> available in the admin guide [1]. The nifi-toolkit is available on the
> downloads page [2].
>
>
>
> 2) NiFi does not support AD groups yet. There is work currently underway
> that will facilitate groups being loaded from an external source.
>
>
>
> Thanks
>
>
>
> Matt
>
>
>
> [1] https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#
> encrypted-passwords-in-configuration-files
>
> [2] https://nifi.apache.org/download.html
>
>
>
> On Fri, May 26, 2017 at 2:15 PM, Shrey Kapoor 
> wrote:
>
> Hi,
>
>
>
> I have a couple of questions.
>
> 1. Is it possible to NOT put the Manager Password, Truststore Password and
> Keystore password in clear text in login-identity-providers.xml file?
>
> 2. Does Nifi support adding AD groups yet?
>
>
>
> Regards,
>
> Shrey
>
>
>
>
>

RE: Nifi Authentication

[Shrey Kapoor]

Hi Matt,

I have nifi-1.1.1-bin.tar.gz installed. But I do not find encrypt-config tool 
in my bin directory. Is encrypt-config tool a part of nifi-toolkit only or Is 
it not a part version 1.1.1 ? Apologies for my ignorance. I am now to nifi.

Regards,
Shrey

From: Matt Gilman [mailto:matt.c.gil...@gmail.com]
Sent: Friday, May 26, 2017 11:38 AM
To: users@nifi.apache.org
Subject: Re: Nifi Authentication

Shrey,

1) I believe that you can use the encrypt-config tool that is part of the 
nifi-toolkit to encrypt the sensitive parts of the login-identity-providers.xml 
file. The documentation for that is available in the admin guide [1]. The 
nifi-toolkit is available on the downloads page [2].

2) NiFi does not support AD groups yet. There is work currently underway that 
will facilitate groups being loaded from an external source.

Thanks

Matt

[1] 
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#encrypted-passwords-in-configuration-files
[2] https://nifi.apache.org/download.html

On Fri, May 26, 2017 at 2:15 PM, Shrey Kapoor 
mailto:shrey.kap...@ds-iq.com>> wrote:

Hi,



I have a couple of questions.

1. Is it possible to NOT put the Manager Password, Truststore Password and 
Keystore password in clear text in login-identity-providers.xml file?

2. Does Nifi support adding AD groups yet?



Regards,

Shrey

RE: CVSReader Controller Service with more properties Suporting Expression Language

[Carlos Manuel Fernandes (DSI)]

Mark,

I created NIFI-3987.

Thanks
Carlos
From: Mark Payne [mailto:marka...@hotmail.com]
Sent: sexta-feira, 26 de maio de 2017 19:15
To: users@nifi.apache.org
Subject: Re: CVSReader Controller Service with more properties Suporting 
Expression Language

Carlos,

Thanks, I'm glad that you're getting some use out of the new record-oriented 
stuff!

You're right, these properties probably do make sense to support Expression 
Language. Do
you mind filing at JIRA [1] to add support for Expression Language for these 
properties?

Thanks
-Mark

[1] https://issues.apache.org/jira/browse/NIFI

On May 26, 2017, at 2:08 PM, Carlos Manuel Fernandes (DSI) 
mailto:carlos.antonio.fernan...@cgd.pt>> wrote:

Congratulations Team for 1.2 release and especially for the Record Oriented 
Paradigm. It’s a great abstraction and permit  create  more concise and 
reusable flows .  My first  experience was  a simple use case:

Create a service who accepts  file  parameters (ex: file.name, 
file.avro.schema, file.separator) and  target table parameters (ex:table.name, 
table.schema)  , get the file and  put   the file data on target Table.   This 
may be made :  HandleHttpRequest  (receiving all the parameters) -> FetchFile  
( using file.name parameter) ->PutDatabaseRecord (schema and table parameters) 
+ CSVReader(with file.avro.schema parameter) -> HandleHttpResponse.

This works and its general, but  CSVReader Controller properties (value 
Separator, Skip Header, quote and Escape ) don’t supports expression Language  
and this limits  the reusability of this Flow Service for files of given 
separator, header, etc.   It’s possible to put expression language Suport  on 
CSVReader fixed properties?

Thanks

Carlos

Re: Nifi Authentication

[Matt Gilman]

Shrey,

1) I believe that you can use the encrypt-config tool that is part of the
nifi-toolkit to encrypt the sensitive parts of the
login-identity-providers.xml file. The documentation for that is available
in the admin guide [1]. The nifi-toolkit is available on the downloads page
[2].

2) NiFi does not support AD groups yet. There is work currently underway
that will facilitate groups being loaded from an external source.

Thanks

Matt

[1]
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#encrypted-passwords-in-configuration-files
[2] https://nifi.apache.org/download.html

On Fri, May 26, 2017 at 2:15 PM, Shrey Kapoor 
wrote:

> Hi,
>
>
>
> I have a couple of questions.
>
> 1. Is it possible to NOT put the Manager Password, Truststore Password and
> Keystore password in clear text in login-identity-providers.xml file?
>
> 2. Does Nifi support adding AD groups yet?
>
>
>
> Regards,
>
> Shrey
>
>
>

Re: CVSReader Controller Service with more properties Suporting Expression Language

[Mark Payne]

Carlos,

Thanks, I'm glad that you're getting some use out of the new record-oriented 
stuff!

You're right, these properties probably do make sense to support Expression 
Language. Do
you mind filing at JIRA [1] to add support for Expression Language for these 
properties?

Thanks
-Mark

[1] https://issues.apache.org/jira/browse/NIFI

On May 26, 2017, at 2:08 PM, Carlos Manuel Fernandes (DSI) 
mailto:carlos.antonio.fernan...@cgd.pt>> wrote:

Congratulations Team for 1.2 release and especially for the Record Oriented 
Paradigm. It’s a great abstraction and permit  create  more concise and 
reusable flows .  My first  experience was  a simple use case:

Create a service who accepts  file  parameters (ex: file.name, 
file.avro.schema, file.separator) and  target table parameters (ex:table.name, 
table.schema)  , get the file and  put   the file data on target Table.   This 
may be made :  HandleHttpRequest  (receiving all the parameters) -> FetchFile  
( using file.name parameter) ->PutDatabaseRecord (schema and table parameters) 
+ CSVReader(with file.avro.schema parameter) -> HandleHttpResponse.

This works and its general, but  CSVReader Controller properties (value 
Separator, Skip Header, quote and Escape ) don’t supports expression Language  
and this limits  the reusability of this Flow Service for files of given 
separator, header, etc.   It’s possible to put expression language Suport  on 
CSVReader fixed properties?

Thanks

Carlos

Nifi Authentication

[Shrey Kapoor]

Hi,



I have a couple of questions.

1. Is it possible to NOT put the Manager Password, Truststore Password and 
Keystore password in clear text in login-identity-providers.xml file?

2. Does Nifi support adding AD groups yet?



Regards,

Shrey

CVSReader Controller Service with more properties Suporting Expression Language

[Carlos Manuel Fernandes (DSI)]

Congratulations Team for 1.2 release and especially for the Record Oriented 
Paradigm. It's a great abstraction and permit  create  more concise and 
reusable flows .  My first  experience was  a simple use case:

Create a service who accepts  file  parameters (ex: file.name, 
file.avro.schema, file.separator) and  target table parameters (ex:table.name, 
table.schema)  , get the file and  put   the file data on target Table.   This 
may be made :  HandleHttpRequest  (receiving all the parameters) -> FetchFile  
( using file.name parameter) ->PutDatabaseRecord (schema and table parameters) 
+ CSVReader(with file.avro.schema parameter) -> HandleHttpResponse.

This works and its general, but  CSVReader Controller properties (value 
Separator, Skip Header, quote and Escape ) don't supports expression Language  
and this limits  the reusability of this Flow Service for files of given 
separator, header, etc.   It's possible to put expression language Suport  on 
CSVReader fixed properties?

Thanks

Carlos

difficulty killing NiFi w/ nifi.sh stop under 1.2.0 now vs. 1.1.2 when run as systemd service

[Jeremy Taylor]

Greetings,
I’m hoping to upgrade the my software team’s baseline to use NiFi 1.2.0.  I’m 
having trouble w/ a particular situation of trying to take nifi down.  Prior to 
this version, I’ve been able to use the nifi.sh script w/o sudo rights to kill 
nifi when it has been brought up by a service (systemd, not init.d).
Main points:
1) We have had auto-deploy working via bitbucket pipelines to a staging system 
that has auto deployed all the nifi required files from our baseline (not nifi 
internal configs).
2) The AWS VM that runs nifi autmatically starts up nifi in a service state via 
systemd services.  We masquerade running it as a non-root user w/ sudo rights, 
but do not use those sudo rights as scripts in bitbucket pipelines won’t 
support sudo rights.
3) The deploy script for our staging server that runs nifi attempts to take 
down nifi with a `nifi.sh stop`, which has worked prior to this version.  The 
newer nifi flow being deployed is manipulated via XSL and then copied in where 
it needs to go before restarting nifi w/ `nifi.sh start` ; (we stop using 
systemd upon the first deploy to the staging system)
4) I’ve done a diff between the latest nifi.sh and the previous nifi.sh from 
1.1.2 and only see a tiny difference.
5) Our staging server starts up every morning and brings up nifi and related 
services via systemd services.
6) I realize using nifi as an init.d service is more supported than using it as 
a systemd service.  However, we’ve not been able to masquerade as a different 
user properly very well when using init.d.  Having to be root for bitbucket 
pipelines would also be a dealbreaker for us.  Thus, having the service being 
run as a user other than root is important to us.
7) For reference, our systemd service file only deals with calling the RunNiFi 
class and does not bother with the nifi shell script.

Questions:
1) Would anyone know why a simple “nifi.sh stop” would no longer kill a 
pre-existing nifi process being run as a systemd service in nifi 1.2.0?
2) We are thinking of attempting a brute force kill that would kill the 
“RunNiFi start” Java process.  We are concerned that not exiting gracefully 
would be really bad for nifi and related nifi repositories.  Would this route 
be recommended anyway in our circumstance?
3) Any further recommendations?

--Jeremy

Re: SplitRecord vs SplitText: fragment attributes

[James Wing]

Uwe,

Please do create a JIRA.  I agree with you that SplitRecord should provide
compatible fragment.* attributes like the older split processors.
Partially for a consistent user experience, and partly for compatibility
with MergeContent and other processors that read the fragment.* attributes.

Thanks,

James

On Fri, May 26, 2017 at 7:17 AM, Uwe Geercken  wrote:

> Hello,
>
> I have used both the SplitRecord and SplitText processors. When using the
> SplitText processor, the flowfile gets various attributes for the fragment
> which in turn can be used to generate a unique filename for the output with
> e.g. PutFile. I was using the fragment.index attribute for this.
>
> The SplitRecord does not create attributes for the fragments. The only
> attribute I can use to generate a unique filename would be the uuid of the
> flowfile. While this is ok for me, I would recommend that the SplitRecord
> would generate similar attributes for the fragments as the SplitText
> processor. And btw: the other SplitXXX processors also have attributes for
> the fragments.
>
> Should I open a jira on this?
>
> Rgds,
>
> Uwe
>

SplitRecord vs SplitText: fragment attributes

[Uwe Geercken]

Hello,

 

I have used both the SplitRecord and SplitText processors. When using the SplitText processor, the flowfile gets various attributes for the fragment which in turn can be used to generate a unique filename for the output with e.g. PutFile. I was using the fragment.index attribute for this.

 

The SplitRecord does not create attributes for the fragments. The only attribute I can use to generate a unique filename would be the uuid of the flowfile. While this is ok for me, I would recommend that the SplitRecord would generate similar attributes for the fragments as the SplitText processor. And btw: the other SplitXXX processors also have attributes for the fragments.

 

Should I open a jira on this?

 

Rgds,

 

Uwe

Re: using rest api to enable transmission in remote process group

[Matt Gilman]

Once the RPG is created it starts communicating with the target instance.
This process is done asynchronously so you will need to wait for that to
complete. The different options are really just the condition that
identifies when the connection can be created. An alternative would be to
loop and GET the RPG with each iteration and break out of your loop once
the desired port is available. At that point, your request to create the
connection should work on the first attempt.

Thanks

Matt

On Fri, May 26, 2017 at 9:08 AM, mohammed shambakey 
wrote:

> Thanks Matt
>
> I used the "/remote-processor-groups//input-ports/"
> with a JSON file that has only "revision", and under
> "remoteProcessGroupPort", it has "id", "groupId" and "transmitting", and it
> worked. (Currently, I'm using NIFI 1.2.0 and the docs says: "This
> endpoint is subject to change as NiFi and it's REST API evolve").
>
> One more thing please, I had to make a loop to make a connection between a
> "processor" and a created "remote process group". In each iteration, I
> check the status of the rest api to find if the connection is created
> successfully or not, otherwise, the loop sleeps for some time then begins
> the next iteration. I just wonder if there is something I should do in NIFI
> configuration to the need for this loop?
>
> Regards
>
> On Thu, May 25, 2017 at 11:06 AM, Matt Gilman 
> wrote:
>
>> Mohammed,
>>
>> I would guess that the request failed and the response body contains an
>> error message and you're attempting to parse that as JSON. I'd suggest
>> inspecting the response codes from the request before attempting to
>> interpret the response body. You can also look at your logs/nifi-user.log
>> for any errors from your request.
>>
>> Thanks
>>
>> Matt
>>
>> On Thu, May 25, 2017 at 10:04 AM, mohammed shambakey <
>> shambak...@gmail.com> wrote:
>>
>>> Hi
>>>
>>> I'm trying to call nifi rest api from Python "request" module (
>>> http://docs.python-requests.org/en/master/) to enable transmission in a
>>> remote process group (I think this is done by changing the "transmitting"
>>> element in the required input port to a boolean "true").
>>>
>>> So, I get the JSON file of the remote process group using this Python
>>> "requests" module commad:
>>>
>>> rpg=requests.get("http://localhost:8085/nifi-api/remote-process-groups/>> of remote process group>").json()
>>> The output json file is attached
>>>
>>> I modified the "transmitting" element of the the input port to boolean
>>> "True", then, I tried to pass the modified JSON file to the following
>>> command
>>>
>>> rpg_new=requests.put("http://localhost:8085/nifi-api/remote-
>>> process-groups/", json=rpg).json()
>>>
>>> But I receive the following error:
>>> "
>>> Traceback (most recent call last):
>>>   File "rpg_nifi_create.py", line 116, in 
>>> rpg_update=requests.put(url_rpg_update+rpg['id'],json=rpg,he
>>> aders=token_header).json()
>>>   File 
>>> "/home/shambakey1/miniconda2/lib/python2.7/site-packages/requests/models.py",
>>> line 826, in json
>>> return complexjson.loads(self.text, **kwargs)
>>>   File "/home/shambakey1/miniconda2/lib/python2.7/json/__init__.py",
>>> line 339, in loads
>>> return _default_decoder.decode(s)
>>>   File "/home/shambakey1/miniconda2/lib/python2.7/json/decoder.py",
>>> line 367, in decode
>>> raise ValueError(errmsg("Extra data", s, end, len(s)))
>>> ValueError: Extra data: line 1 column 2 - line 1 column 63 (char 1 - 62)
>>> "
>>>
>>> I tried to truncate the passed JSON file such that it contains
>>> information only about "revision" and the modified "inputPorts" list, but
>>> still the same problem.
>>>
>>> I can the JSON file (before and after modification) using jsonview, so I
>>> think there is nothing wrong the JSON structure (e.g., no independent
>>> dictionaries). I don't know what is the problem?
>>>
>>> Regards
>>>
>>> --
>>> Mohammed
>>>
>>
>>
>
>
> --
> Mohammed
>

Re: using rest api to enable transmission in remote process group

[mohammed shambakey]

Thanks Matt

I used the "/remote-processor-groups//input-ports/" with
a JSON file that has only "revision", and under "remoteProcessGroupPort",
it has "id", "groupId" and "transmitting", and it worked. (Currently, I'm
using NIFI 1.2.0 and the docs says: "This endpoint is subject to change as
NiFi and it's REST API evolve").

One more thing please, I had to make a loop to make a connection between a
"processor" and a created "remote process group". In each iteration, I
check the status of the rest api to find if the connection is created
successfully or not, otherwise, the loop sleeps for some time then begins
the next iteration. I just wonder if there is something I should do in NIFI
configuration to the need for this loop?

Regards

On Thu, May 25, 2017 at 11:06 AM, Matt Gilman 
wrote:

> Mohammed,
>
> I would guess that the request failed and the response body contains an
> error message and you're attempting to parse that as JSON. I'd suggest
> inspecting the response codes from the request before attempting to
> interpret the response body. You can also look at your logs/nifi-user.log
> for any errors from your request.
>
> Thanks
>
> Matt
>
> On Thu, May 25, 2017 at 10:04 AM, mohammed shambakey  > wrote:
>
>> Hi
>>
>> I'm trying to call nifi rest api from Python "request" module (
>> http://docs.python-requests.org/en/master/) to enable transmission in a
>> remote process group (I think this is done by changing the "transmitting"
>> element in the required input port to a boolean "true").
>>
>> So, I get the JSON file of the remote process group using this Python
>> "requests" module commad:
>>
>> rpg=requests.get("http://localhost:8085/nifi-api/remote-process-groups/> of remote process group>").json()
>> The output json file is attached
>>
>> I modified the "transmitting" element of the the input port to boolean
>> "True", then, I tried to pass the modified JSON file to the following
>> command
>>
>> rpg_new=requests.put("http://localhost:8085/nifi-api/remote-
>> process-groups/", json=rpg).json()
>>
>> But I receive the following error:
>> "
>> Traceback (most recent call last):
>>   File "rpg_nifi_create.py", line 116, in 
>> rpg_update=requests.put(url_rpg_update+rpg['id'],json=rpg,he
>> aders=token_header).json()
>>   File 
>> "/home/shambakey1/miniconda2/lib/python2.7/site-packages/requests/models.py",
>> line 826, in json
>> return complexjson.loads(self.text, **kwargs)
>>   File "/home/shambakey1/miniconda2/lib/python2.7/json/__init__.py",
>> line 339, in loads
>> return _default_decoder.decode(s)
>>   File "/home/shambakey1/miniconda2/lib/python2.7/json/decoder.py", line
>> 367, in decode
>> raise ValueError(errmsg("Extra data", s, end, len(s)))
>> ValueError: Extra data: line 1 column 2 - line 1 column 63 (char 1 - 62)
>> "
>>
>> I tried to truncate the passed JSON file such that it contains
>> information only about "revision" and the modified "inputPorts" list, but
>> still the same problem.
>>
>> I can the JSON file (before and after modification) using jsonview, so I
>> think there is nothing wrong the JSON structure (e.g., no independent
>> dictionaries). I don't know what is the problem?
>>
>> Regards
>>
>> --
>> Mohammed
>>
>
>


-- 
Mohammed

Re: NIFI startup error

[Matt Gilman]

Ben,

The warning in your log is simply letting the developer of those components
know that the bundle is not following the suggested best practices [1].
NiFi has detected this but will not have any ill effects based on other
isolated classpath configurations and referencing components. If the
configuration would cause the component to not functional correctly, an
error would have been logged and the component would have been skipped.
This has been described more here [2] (specifically the last paragraph in
that section).

Thanks

Matt

[1] https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html#nars
[2]
https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html#per-instance-classloading

On Fri, May 26, 2017 at 3:34 AM, 尹文才  wrote:

> Sorry for that the reason why my NIFI didn't get up is not due to the
> warning listed above, but I still wonder why there're such warnings.
>
> Regards,
> Ben
>
> 2017-05-26 15:06 GMT+08:00 尹文才 :
>
>> Hi guys, I'm currently writing a customized NIFI processor and after
>> putting the nar into the lib folder
>> and tried to relaunch NIFI, it was giving a bunch of following errors:
>>
>> 2017-05-26 14:52:33,183 WARN [main] org.apache.nifi.nar.ExtensionManager
>> Controller Service org.apache.nifi.couchbase.CouchbaseClusterService is
>> bundled with its supporting APIs 
>> org.apache.nifi.couchbase.CouchbaseClusterControllerService.
>> The service APIs should not be bundled with the implementations.
>> 2017-05-26 14:52:33,198 WARN [main] org.apache.nifi.nar.ExtensionManager
>> Component org.apache.nifi.processors.couchbase.GetCouchbaseKey is
>> bundled with its referenced Controller Service APIs
>> org.apache.nifi.couchbase.CouchbaseClusterControllerService. The service
>> APIs should not be bundled with component implementations that reference it.
>> 2017-05-26 14:52:33,214 WARN [main] org.apache.nifi.nar.ExtensionManager
>> Component org.apache.nifi.processors.couchbase.PutCouchbaseKey is
>> bundled with its referenced Controller Service APIs
>> org.apache.nifi.couchbase.CouchbaseClusterControllerService. The service
>> APIs should not be bundled with component implementations that reference it.
>> 2017-05-26 14:52:33,355 WARN [main] org.apache.nifi.nar.ExtensionManager
>> Controller Service org.apache.nifi.processors.gcp
>> .credentials.service.GCPCredentialsControllerService is bundled with its
>> supporting APIs org.apache.nifi.processors.gcp
>> .credentials.service.GCPCredentialsService. The service APIs should not
>> be bundled with the implementations.
>> 2017-05-26 14:52:33,417 WARN [main] org.apache.nifi.nar.ExtensionManager
>> Component org.apache.nifi.processors.gcp.storage.PutGCSObject is bundled
>> with its referenced Controller Service APIs org.apache.nifi.processors.gcp
>> .credentials.service.GCPCredentialsService. The service APIs should not
>> be bundled with component implementations that reference it.
>> 2017-05-26 14:52:33,417 WARN [main] org.apache.nifi.nar.ExtensionManager
>> Component org.apache.nifi.processors.gcp.storage.FetchGCSObject is
>> bundled with its referenced Controller Service APIs
>> org.apache.nifi.processors.gcp.credentials.service.GCPCredentialsService.
>> The service APIs should not be bundled with component implementations that
>> reference it.
>> 2017-05-26 14:52:33,417 WARN [main] org.apache.nifi.nar.ExtensionManager
>> Component org.apache.nifi.processors.gcp.storage.DeleteGCSObject is
>> bundled with its referenced Controller Service APIs
>> org.apache.nifi.processors.gcp.credentials.service.GCPCredentialsService.
>> The service APIs should not be bundled with component implementations that
>> reference it.
>> 2017-05-26 14:52:33,433 WARN [main] org.apache.nifi.nar.ExtensionManager
>> Component org.apache.nifi.processors.gcp.storage.ListGCSBucket is
>> bundled with its referenced Controller Service APIs
>> org.apache.nifi.processors.gcp.credentials.service.GCPCredentialsService.
>> The service APIs should not be bundled with component implementations that
>> reference it.
>> 2017-05-26 14:52:34,511 WARN [main] org.apache.nifi.nar.ExtensionManager
>> Controller Service org.apache.nifi.processors.aws
>> .credentials.provider.service.AWSCredentialsProviderControllerService is
>> bundled with its supporting APIs org.apache.nifi.processors.aws
>> .credentials.provider.service.AWSCredentialsProviderService. The service
>> APIs should not be bundled with the implementations.
>> 2017-05-26 14:52:34,543 WARN [main] org.apache.nifi.nar.ExtensionManager
>> Component org.apache.nifi.processors.aws.s3.FetchS3Object is bundled
>> with its referenced Controller Service APIs org.apache.nifi.processors.aws
>> .credentials.provider.service.AWSCredentialsProviderService. The service
>> APIs should not be bundled with component implementations that reference it.
>> 2017-05-26 14:52:34,558 WARN [main] org.apache.nifi.nar.ExtensionManager
>> Component org.apache.nifi.processors.aws.s3.PutS3Object is bundled with
>> its referenced Contro

Re: How to find week of the year for the date value?

[Mark Payne]

Prabhu,

You can use the "toDate" function to convert that string into a Date and then 
use
the "format" function to convert that date into what you want using the 
patterns defined
for SimpleDateFormat. You can see what those patterns/symbols mean and examples
at [1]. I hope this helps.

Thanks
-Mark

[1] https://docs.oracle.com/javase/8/docs/api/java/text/SimpleDateFormat.html



On May 26, 2017, at 8:35 AM, prabhu Mahendran 
mailto:prabhuu161...@gmail.com>> wrote:


My Flow having attribute '05-05-2015'.And i need to find week of the date in 
NiFi.

For example:

if date is 05 then it is belongs to 1st week of the year.


I shouldn't use Script/Program for find out week.

i need to find out that using NiFi Expression language only.

Can anyone suggest way to do that?

How to find week of the year for the date value?

[prabhu Mahendran]

My Flow having attribute '05-05-2015'.And i need to find week of the date
in NiFi.

For example:

if date is 05 then it is belongs to 1st week of the year.

I shouldn't use Script/Program for find out week.

i need to find out that using NiFi Expression language only.

Can anyone suggest way to do that?

Re: some processors runs only once in NiFi

[prabhu Mahendran]

Hi Koji,

Thanks for your explanation

Many thanks
prabhu

On Fri, May 26, 2017 at 9:40 AM, Koji Kawamura 
wrote:

> Hi Prabhu,
>
> Same as ListHDFS, GetHTTP uses ETAG HTTP header, and if server returns
> NOT_MODIFIED(304), it doesn't create output FlowFile. The screenshot
> indicates that GetHTTP runs 61 times but it only creates output
> FlowFile once because it's not modified.
>
> I believe that is what's happening.
>
> Thanks,
> Koji
>
> On Wed, May 24, 2017 at 2:30 PM, prabhu Mahendran
>  wrote:
> > Pierre,
> >
> > Thanks for your mail,
> >
> > I might try to list files over and over.So that may be problem i faced.I
> > just modified existing files in hdfs and then list those files using
> > ListHDFS.
> >
> > I could be list files in which same as well as last execution of a
> processor
> > that's may be problem.
> >
> > Many thanks
> >
> >
> > On Wed, May 24, 2017 at 10:45 AM, Pierre Villard
> >  wrote:
> >>
> >> Just a quick remark, the ListHDFS processor won't list files over and
> >> over, it'll only list new files since the last execution of the
> processor.
> >> Do you know if new files are generated in the directory your are
> listing?
> >>
> >> Screenshots of your configurations would definitely help.
> >>
> >> 2017-05-24 6:55 GMT+02:00 Joe Witt :
> >>>
> >>> prabhu - can you please share screenshots and or logs showing that it
> >>> is running only once?
> >>>
> >>> Thanks
> >>>
> >>> On Wed, May 24, 2017 at 12:42 AM, prabhu Mahendran
> >>>  wrote:
> >>> > Aldrin,
> >>> >
> >>> > Thanks for your response.
> >>> >
> >>> > For GetHTTP ,I have checked to download different files even it could
> >>> > not
> >>> > run more than once.
> >>> >
> >>> > ListHDFS:I have used NiFi-1.2.0 in which configured these attributes
> >>> > "Hadoop
> >>> > Configuration Resources","Directory","RecurseSubDirectories"
> correctly
> >>> > for
> >>> > Hadoop-2.5.2.This runs only once not run again.
> >>> >
> >>> > Note: I have checked those processors in windows.
> >>> >
> >>> > Can you give any suggestion to solve this?
> >>> >
> >>> > Many Thanks,
> >>> >
> >>> >
> >>> > On Tue, May 23, 2017 at 7:03 PM, Aldrin Piri 
> >>> > wrote:
> >>> >>
> >>> >> For GetHTTP, this processor makes use of ETags[1] to prevent
> >>> >> downloading
> >>> >> the same resource repeatedly.  I would speculate that this is the
> case
> >>> >> for
> >>> >> the resource you are specifying.
> >>> >>
> >>> >> As for ListHDFS, could you specify what version you are using?
> There
> >>> >> have
> >>> >> been some bugs concerning how this was handled.  If the version is
> the
> >>> >> latest, could you please provide some more details in terms of
> >>> >> structure and
> >>> >> timestamps of the associated files causing the issue you are
> >>> >> describing?
> >>> >>
> >>> >>
> >>> >> [1] https://en.wikipedia.org/wiki/HTTP_ETag
> >>> >>
> >>> >> On Tue, May 23, 2017 at 3:22 AM, prabhu Mahendran
> >>> >>  wrote:
> >>> >>>
> >>> >>> Since i have faced some unexpected behaviour's in NiFi.
> >>> >>>
> >>> >>> I don't know why those processors which doesn't run more than once.
> >>> >>>
> >>> >>>
> >>> >>> For example:
> >>> >>>
> >>> >>> 1.GetHTTP:
> >>> >>>
> >>> >>> I have used GetHTTP processor for download files from "HTTP" Url.
> >>> >>> Initially i have scheduled 0 sec
> >>> >>>
> >>> >>> If i runs the processor it runs only once and not again run.Once
> copy
> >>> >>> the
> >>> >>> same processor and paste in the UI then click run that processor it
> >>> >>> again
> >>> >>> runs only once.
> >>> >>>
> >>> >>> If i scheduling it then also not runs more than once.
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>> 2.ListHDFS:
> >>> >>>
> >>> >>> I have configured local cluster properties in ListHDFS.
> >>> >>>
> >>> >>> i have 12 files in hdfs directory.If i runs without scheduling then
> >>> >>> it
> >>> >>> lists 12 files correctly and after scheduling it only returns 11
> >>> >>> files
> >>> >>> without 1 file and not run after first time run
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>> can anyone explain the behaviour of those processsors when 1 day
> >>> >>> scheduling in TimerDriven?
> >>> >>
> >>> >>
> >>> >
> >>
> >>
> >
>

Re: NIFI startup error

[尹文才]

Sorry for that the reason why my NIFI didn't get up is not due to the
warning listed above, but I still wonder why there're such warnings.

Regards,
Ben

2017-05-26 15:06 GMT+08:00 尹文才 :

> Hi guys, I'm currently writing a customized NIFI processor and after
> putting the nar into the lib folder
> and tried to relaunch NIFI, it was giving a bunch of following errors:
>
> 2017-05-26 14:52:33,183 WARN [main] org.apache.nifi.nar.ExtensionManager
> Controller Service org.apache.nifi.couchbase.CouchbaseClusterService is
> bundled with its supporting APIs org.apache.nifi.couchbase.
> CouchbaseClusterControllerService. The service APIs should not be bundled
> with the implementations.
> 2017-05-26 14:52:33,198 WARN [main] org.apache.nifi.nar.ExtensionManager
> Component org.apache.nifi.processors.couchbase.GetCouchbaseKey is bundled
> with its referenced Controller Service APIs org.apache.nifi.couchbase.
> CouchbaseClusterControllerService. The service APIs should not be bundled
> with component implementations that reference it.
> 2017-05-26 14:52:33,214 WARN [main] org.apache.nifi.nar.ExtensionManager
> Component org.apache.nifi.processors.couchbase.PutCouchbaseKey is bundled
> with its referenced Controller Service APIs org.apache.nifi.couchbase.
> CouchbaseClusterControllerService. The service APIs should not be bundled
> with component implementations that reference it.
> 2017-05-26 14:52:33,355 WARN [main] org.apache.nifi.nar.ExtensionManager
> Controller Service org.apache.nifi.processors.gcp.credentials.service.
> GCPCredentialsControllerService is bundled with its supporting APIs
> org.apache.nifi.processors.gcp.credentials.service.GCPCredentialsService.
> The service APIs should not be bundled with the implementations.
> 2017-05-26 14:52:33,417 WARN [main] org.apache.nifi.nar.ExtensionManager
> Component org.apache.nifi.processors.gcp.storage.PutGCSObject is bundled
> with its referenced Controller Service APIs org.apache.nifi.processors.
> gcp.credentials.service.GCPCredentialsService. The service APIs should
> not be bundled with component implementations that reference it.
> 2017-05-26 14:52:33,417 WARN [main] org.apache.nifi.nar.ExtensionManager
> Component org.apache.nifi.processors.gcp.storage.FetchGCSObject is
> bundled with its referenced Controller Service APIs
> org.apache.nifi.processors.gcp.credentials.service.GCPCredentialsService.
> The service APIs should not be bundled with component implementations that
> reference it.
> 2017-05-26 14:52:33,417 WARN [main] org.apache.nifi.nar.ExtensionManager
> Component org.apache.nifi.processors.gcp.storage.DeleteGCSObject is
> bundled with its referenced Controller Service APIs
> org.apache.nifi.processors.gcp.credentials.service.GCPCredentialsService.
> The service APIs should not be bundled with component implementations that
> reference it.
> 2017-05-26 14:52:33,433 WARN [main] org.apache.nifi.nar.ExtensionManager
> Component org.apache.nifi.processors.gcp.storage.ListGCSBucket is bundled
> with its referenced Controller Service APIs org.apache.nifi.processors.
> gcp.credentials.service.GCPCredentialsService. The service APIs should
> not be bundled with component implementations that reference it.
> 2017-05-26 14:52:34,511 WARN [main] org.apache.nifi.nar.ExtensionManager
> Controller Service org.apache.nifi.processors.aws.credentials.provider.
> service.AWSCredentialsProviderControllerService is bundled with its
> supporting APIs org.apache.nifi.processors.aws.credentials.provider.
> service.AWSCredentialsProviderService. The service APIs should not be
> bundled with the implementations.
> 2017-05-26 14:52:34,543 WARN [main] org.apache.nifi.nar.ExtensionManager
> Component org.apache.nifi.processors.aws.s3.FetchS3Object is bundled with
> its referenced Controller Service APIs org.apache.nifi.processors.
> aws.credentials.provider.service.AWSCredentialsProviderService. The
> service APIs should not be bundled with component implementations that
> reference it.
> 2017-05-26 14:52:34,558 WARN [main] org.apache.nifi.nar.ExtensionManager
> Component org.apache.nifi.processors.aws.s3.PutS3Object is bundled with
> its referenced Controller Service APIs org.apache.nifi.processors.
> aws.credentials.provider.service.AWSCredentialsProviderService. The
> service APIs should not be bundled with component implementations that
> reference it.
> 2017-05-26 14:52:34,558 WARN [main] org.apache.nifi.nar.ExtensionManager
> Component org.apache.nifi.processors.aws.s3.DeleteS3Object is bundled
> with its referenced Controller Service APIs org.apache.nifi.processors.
> aws.credentials.provider.service.AWSCredentialsProviderService. The
> service APIs should not be bundled with component implementations that
> reference it.
> 2017-05-26 14:52:34,558 WARN [main] org.apache.nifi.nar.ExtensionManager
> Component org.apache.nifi.processors.aws.s3.ListS3 is bundled with its
> referenced Controller Service APIs org.apache.nifi.processors.
> aws.credentials.provider.service.A

Re: use DistributedMapCacheClientService in NIFI cluster

[尹文才]

Thanks Michal, I only need to keep very few config data, so zookeeper
should be sufficient for me.😁

2017-05-26 15:12 GMT+08:00 Michal Klempa :

> Hi Ben,
> according to my experience, I would recommend not to use
> DistributedMapCache at all.
> First of all - its not load balanced / HA and then, it is just a
> HashMap implementation in Java, talking to clients using simple TCP
> (=it consumes RAM from NiFi's Java heap space)
> I guess its in NiFi as a safety net, for simple use cases.
> For any production / heavy traffic use case, I would go for external
> caching / databases (Redis?)
> ZooKeeper is good for any HA / balanced use case, which does not have
> heavy traffic, so if you have it installed and you know how to do it
> in ZooKeeper, go for it.
>
> Regards,
> Michal
>
> On Fri, May 26, 2017 at 2:19 AM, 尹文才  wrote:
> > Thanks Joe, actually what I want to achieve is one of my processors need
> to
> > write some config data to be kept in cluster so that other processors
> would
> > be able to easily get the config data from the cluster.
> > I've considered using the default NIFI state map to do it, but as I know
> it
> > could only keep data for a specific processor and it could only be
> retrieved
> > by that processor. I've never used Hazelcast, I may
> > just keep the config data in Zookeeper directly.
> >
> > Regards,
> > ben
> >
> > 2017-05-26 8:55 GMT+08:00 Joe Witt :
> >>
> >> So the client would be on each of nodea, nodeb, and nodec.  The server
> >> would be on nodea, nodeb, nodec.  Each client would be configured to
> >> talk to any one of the three servers nodea, nodeb, or nodec.  It does
> >> not offer HA.  For more complete behavior it is a good idea to have a
> >> client/service implementation that talks to a full caching service.
> >> In the next release you can script out a controller service as a cache
> >> client.  I believe one of the folks in the community has an example
> >> floating around on how to do this to talk to Hazelcast.
> >>
> >> Thanks
> >> Joe
> >>
> >> On Thu, May 25, 2017 at 8:45 PM, 尹文才  wrote:
> >> > Thanks Joe, so  I need to setup the DistributedMapCacheServer on all
> >> > nodes,
> >> > do you mean all DistributedMapCacheClientService should reference
> only
> >> > one
> >> > of the servers(the same one on the same node)?
> >> > What if the DistributedMapCacheServer goes down on that node(or the
> node
> >> > itself goes down), does it support HA?
> >> >
> >> >
> >> > 2017-05-25 20:46 GMT+08:00 Joe Witt :
> >> >>
> >> >> Hello
> >> >>
> >> >> You put the DistributedMapCacheServer controller service on as well
> >> >> and then point at it from the client services.  So in your three
> nodes
> >> >> all three will have the server service but on all the clients they'll
> >> >> only point to the server service on one of the nodes.
> >> >>
> >> >> Thanks
> >> >> Joe
> >> >>
> >> >> On Thu, May 25, 2017 at 5:29 AM, 尹文才  wrote:
> >> >> > Hi guys, I'm currently using NIFI with 3 nodes as a cluster, when
> >> >> > using
> >> >> > DistributedMapCacheClientService there's a configuration property
> >> >> > called 'Server Hostname'. I've tried with localhost on my local
> NIFI
> >> >> > standlone node
> >> >> > and it did work. My question is what should I set inside the NIFI
> >> >> > cluster?
> >> >> > Thanks.
> >> >
> >> >
> >
> >
>

Re: use DistributedMapCacheClientService in NIFI cluster

[Michal Klempa]

Hi Ben,
according to my experience, I would recommend not to use
DistributedMapCache at all.
First of all - its not load balanced / HA and then, it is just a
HashMap implementation in Java, talking to clients using simple TCP
(=it consumes RAM from NiFi's Java heap space)
I guess its in NiFi as a safety net, for simple use cases.
For any production / heavy traffic use case, I would go for external
caching / databases (Redis?)
ZooKeeper is good for any HA / balanced use case, which does not have
heavy traffic, so if you have it installed and you know how to do it
in ZooKeeper, go for it.

Regards,
Michal

On Fri, May 26, 2017 at 2:19 AM, 尹文才  wrote:
> Thanks Joe, actually what I want to achieve is one of my processors need to
> write some config data to be kept in cluster so that other processors would
> be able to easily get the config data from the cluster.
> I've considered using the default NIFI state map to do it, but as I know it
> could only keep data for a specific processor and it could only be retrieved
> by that processor. I've never used Hazelcast, I may
> just keep the config data in Zookeeper directly.
>
> Regards,
> ben
>
> 2017-05-26 8:55 GMT+08:00 Joe Witt :
>>
>> So the client would be on each of nodea, nodeb, and nodec.  The server
>> would be on nodea, nodeb, nodec.  Each client would be configured to
>> talk to any one of the three servers nodea, nodeb, or nodec.  It does
>> not offer HA.  For more complete behavior it is a good idea to have a
>> client/service implementation that talks to a full caching service.
>> In the next release you can script out a controller service as a cache
>> client.  I believe one of the folks in the community has an example
>> floating around on how to do this to talk to Hazelcast.
>>
>> Thanks
>> Joe
>>
>> On Thu, May 25, 2017 at 8:45 PM, 尹文才  wrote:
>> > Thanks Joe, so  I need to setup the DistributedMapCacheServer on all
>> > nodes,
>> > do you mean all DistributedMapCacheClientService should reference only
>> > one
>> > of the servers(the same one on the same node)?
>> > What if the DistributedMapCacheServer goes down on that node(or the node
>> > itself goes down), does it support HA?
>> >
>> >
>> > 2017-05-25 20:46 GMT+08:00 Joe Witt :
>> >>
>> >> Hello
>> >>
>> >> You put the DistributedMapCacheServer controller service on as well
>> >> and then point at it from the client services.  So in your three nodes
>> >> all three will have the server service but on all the clients they'll
>> >> only point to the server service on one of the nodes.
>> >>
>> >> Thanks
>> >> Joe
>> >>
>> >> On Thu, May 25, 2017 at 5:29 AM, 尹文才  wrote:
>> >> > Hi guys, I'm currently using NIFI with 3 nodes as a cluster, when
>> >> > using
>> >> > DistributedMapCacheClientService there's a configuration property
>> >> > called 'Server Hostname'. I've tried with localhost on my local NIFI
>> >> > standlone node
>> >> > and it did work. My question is what should I set inside the NIFI
>> >> > cluster?
>> >> > Thanks.
>> >
>> >
>
>

NIFI startup error

[尹文才]

Hi guys, I'm currently writing a customized NIFI processor and after
putting the nar into the lib folder
and tried to relaunch NIFI, it was giving a bunch of following errors:

2017-05-26 14:52:33,183 WARN [main] org.apache.nifi.nar.ExtensionManager
Controller Service org.apache.nifi.couchbase.CouchbaseClusterService is
bundled with its supporting APIs
org.apache.nifi.couchbase.CouchbaseClusterControllerService. The service
APIs should not be bundled with the implementations.
2017-05-26 14:52:33,198 WARN [main] org.apache.nifi.nar.ExtensionManager
Component org.apache.nifi.processors.couchbase.GetCouchbaseKey is bundled
with its referenced Controller Service APIs
org.apache.nifi.couchbase.CouchbaseClusterControllerService. The service
APIs should not be bundled with component implementations that reference it.
2017-05-26 14:52:33,214 WARN [main] org.apache.nifi.nar.ExtensionManager
Component org.apache.nifi.processors.couchbase.PutCouchbaseKey is bundled
with its referenced Controller Service APIs
org.apache.nifi.couchbase.CouchbaseClusterControllerService. The service
APIs should not be bundled with component implementations that reference it.
2017-05-26 14:52:33,355 WARN [main] org.apache.nifi.nar.ExtensionManager
Controller Service
org.apache.nifi.processors.gcp.credentials.service.GCPCredentialsControllerService
is bundled with its supporting APIs
org.apache.nifi.processors.gcp.credentials.service.GCPCredentialsService.
The service APIs should not be bundled with the implementations.
2017-05-26 14:52:33,417 WARN [main] org.apache.nifi.nar.ExtensionManager
Component org.apache.nifi.processors.gcp.storage.PutGCSObject is bundled
with its referenced Controller Service APIs
org.apache.nifi.processors.gcp.credentials.service.GCPCredentialsService.
The service APIs should not be bundled with component implementations that
reference it.
2017-05-26 14:52:33,417 WARN [main] org.apache.nifi.nar.ExtensionManager
Component org.apache.nifi.processors.gcp.storage.FetchGCSObject is bundled
with its referenced Controller Service APIs
org.apache.nifi.processors.gcp.credentials.service.GCPCredentialsService.
The service APIs should not be bundled with component implementations that
reference it.
2017-05-26 14:52:33,417 WARN [main] org.apache.nifi.nar.ExtensionManager
Component org.apache.nifi.processors.gcp.storage.DeleteGCSObject is bundled
with its referenced Controller Service APIs
org.apache.nifi.processors.gcp.credentials.service.GCPCredentialsService.
The service APIs should not be bundled with component implementations that
reference it.
2017-05-26 14:52:33,433 WARN [main] org.apache.nifi.nar.ExtensionManager
Component org.apache.nifi.processors.gcp.storage.ListGCSBucket is bundled
with its referenced Controller Service APIs
org.apache.nifi.processors.gcp.credentials.service.GCPCredentialsService.
The service APIs should not be bundled with component implementations that
reference it.
2017-05-26 14:52:34,511 WARN [main] org.apache.nifi.nar.ExtensionManager
Controller Service
org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderControllerService
is bundled with its supporting APIs
org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderService.
The service APIs should not be bundled with the implementations.
2017-05-26 14:52:34,543 WARN [main] org.apache.nifi.nar.ExtensionManager
Component org.apache.nifi.processors.aws.s3.FetchS3Object is bundled with
its referenced Controller Service APIs
org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderService.
The service APIs should not be bundled with component implementations that
reference it.
2017-05-26 14:52:34,558 WARN [main] org.apache.nifi.nar.ExtensionManager
Component org.apache.nifi.processors.aws.s3.PutS3Object is bundled with its
referenced Controller Service APIs
org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderService.
The service APIs should not be bundled with component implementations that
reference it.
2017-05-26 14:52:34,558 WARN [main] org.apache.nifi.nar.ExtensionManager
Component org.apache.nifi.processors.aws.s3.DeleteS3Object is bundled with
its referenced Controller Service APIs
org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderService.
The service APIs should not be bundled with component implementations that
reference it.
2017-05-26 14:52:34,558 WARN [main] org.apache.nifi.nar.ExtensionManager
Component org.apache.nifi.processors.aws.s3.ListS3 is bundled with its
referenced Controller Service APIs
org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderService.
The service APIs should not be bundled with component implementations that
reference it.
2017-05-26 14:52:34,589 WARN [main] org.apache.nifi.nar.ExtensionManager
Component org.apache.nifi.processors.aws.sns.PutSNS is bundled with its
referenced Controller Service APIs
org.apache.nifi.processors.aws.credentials.provi