Member since
09-29-2015
871
Posts
723
Kudos Received
255
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 4268 | 12-03-2018 02:26 PM | |
| 3208 | 10-16-2018 01:37 PM | |
| 4314 | 10-03-2018 06:34 PM | |
| 3173 | 09-05-2018 07:44 PM | |
| 2431 | 09-05-2018 07:31 PM |
02-14-2017
05:26 PM
2 Kudos
The second error looks like it is related to this bug: https://issues.apache.org/jira/browse/NIFI-3389 Essentially you probably have a long attribute value that is exceeding 65535 bytes. Not sure if that is what is resulting in the flow file repo blacklisting the partitions, but it could be related.
... View more
02-13-2017
10:58 PM
1 Kudo
Yes I agree with Matt... once the initial admin has access to the UI, there should be no hand-edits to users.xml or authorizations.xml, everything should be done from the UI.
... View more
02-13-2017
10:24 PM
In 1.x the initial admin can grant access to the other users through the UI by adding a user from the global menu in the top-right and creating a user with the DN of their cert, then give that user access to the resources they should be able to access (i.e. the root group or a individual process group). There are no more true roles in 1.x, although you can simulate them using groups, but in general everything on the canvas can have a policy that defines the users or groups who can take action on it.
... View more
02-10-2017
08:36 PM
I think the best thing to do would be to turn on SSL debug in NiFi... in bootstrap.conf add: java.arg.15=-Djavax.net.debug=all:handshake:verbose Then restart NiFi and try to access the UI and grab the output from nifi-bootstrap.log and we should be able to see what is happening during the handshake.
... View more
02-10-2017
08:24 PM
1 Kudo
@Raj B Thanks! Since the NCM didn't do any data processing there is actually not much different for this article between 0.x and 1.x. The only real difference is when setting up site-to-site connections you now create a remote process group and use the URL of any node in the cluster, where as before you entered the URL of the NCM. Other than that just pretend the NCM isn't in the diagrams and you should be good to go.
... View more
02-10-2017
06:59 PM
2 Kudos
The Compression Level property doesn't look like it supports expression language. The docs should say which properties do.
... View more
02-10-2017
06:23 PM
Is it possible that Firefox isn't letting you connect to certain versions of TLS? I was looking at this: https://support.mozilla.org/t5/Firefox/Hi-I-I-receive-a-quot-Secure-Connection-Failed-quot-warning-when/m-p/1046539
... View more
02-10-2017
05:13 PM
I would expect NiFi 1.1.1 to work with TLS 1.0. When you say the UI won't load, is your browser making it to the NiFi page and then you get access denied? or is the browser failing to make the connection all together?
... View more
02-07-2017
02:10 PM
1 Kudo
Oh right it doesn't show the id in the UI, you will have to first query for all of the templates using this call: http://localhost:8080/nifi-api/flow/templates Then you can find the id of the template you want.
... View more
02-07-2017
01:40 PM
1 Kudo
Every component in NiFi has a UUID. For process groups you can see the id in the left hand palette when it is selected, for templates the id should be in the table that lists the templates.
... View more