Member since
07-30-2019
944
Posts
197
Kudos Received
91
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1506 | 10-05-2021 01:53 PM | |
| 16323 | 09-23-2019 06:03 AM | |
| 6817 | 05-04-2019 08:42 PM | |
| 1502 | 06-11-2018 12:45 PM | |
| 12623 | 06-04-2018 01:11 PM |
09-01-2017
05:17 PM
@Alvin Jin Remove the space between "OU =NIFI" so it looks like "OU=NIFI". Also, don't forget to remove the old users.xml and authorizations.xml files before restarting NiFi. You should stick with released versions, instead of using the snapshot version.
... View more
08-31-2017
08:55 PM
1 Kudo
@Alvin Jin
That authorizers.xml file looks a little off. This is what it should look like: <authorizers>
<authorizer>
<identifier>file-provider</identifier>
<class>org.apache.nifi.authorization.FileAuthorizer</class>
<property name="Authorizations File">./conf/authorizations.xml</property>
<property name="Users File">./conf/users.xml</property>
<property name="Initial Admin Identity">CN=nifiadmin, OU= NIFI.COM</property>
<property name="Legacy Authorized Users File"></property>
<!-- Provide the identity (typically a DN) of each node when clustered, see above description of Node Identity. -->
<property name="Node Identity 1">CN=nifi-0, OU=NIFI.COM</property>
<property name="Node Identity 2">CN=nifi-1, OU=NIFI.COM</property>
<property name="Node Identity 2">CN=nifi-2, OU=NIFI.COM</property>
</authorizer>
</authorizers>
You will have to remove the current users.xml and authorizations.xml file so NiFi will recreate them on restart.
... View more
08-31-2017
12:33 PM
@regie canada The processor can do that, just set the Keep Source File property to false and the file will be deleted.
... View more
08-30-2017
09:17 PM
@regie canada Did you try the above solution?
... View more
08-30-2017
09:12 PM
@Saikrishna Tarapareddy Look at this article, it should help you: User management in NiFi through identity mapping patterns
... View more
08-30-2017
07:03 PM
@Saikrishna Tarapareddy This should be a different question, not a continuation of your first question. Because, now you are asking about authorization, not authentication.
... View more
08-30-2017
03:30 PM
@Mahmoud Yusuf
In my experience, if you aren't making a call to a system level command, then the processor does have an issue sometimes. Try putting the actual "spark-submit <path to jar>" into a shell script and then call the shell script in the ExecuteStreamCommand processor. I have found that method more reliable.
... View more
08-30-2017
12:51 PM
@Mahmoud Yusuf When you say about a minute, does that mean less than a minute or more than a minute? Why don't you try generating a flow file every 2 minutes and see if that works better? Or is it possible to run the script in parallel? Give the ExecuteStreamCommand processor 2 concurrent tasks instead of one.
... View more
08-30-2017
12:22 PM
@Mahmoud Yusuf The reason you cannot stop the ExecuteStreamCommand processor, is that it still has a running thread. How long does it take to run your script outside of NiFi? It seems like the script is not finishing, so the ExecuteStreamCommand processor it just waiting.
... View more