Member since
09-27-2018
138
Posts
23
Kudos Received
10
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
9500 | 02-28-2021 10:23 PM | |
1897 | 02-08-2021 11:53 PM | |
31261 | 12-16-2020 11:31 PM | |
7458 | 12-14-2020 11:02 PM | |
4764 | 12-14-2020 12:18 AM |
01-08-2020
03:44 AM
Hi all,
tried to use the new parameter thing on PutEmail processor in 1.10.0.
Checked spelling and value a thousand times.
Doing the same thing with variables works fine.
Any help is appreciated!
... View more
Labels:
- Labels:
-
Apache NiFi
10-10-2019
06:27 AM
@patrick_hochste Hi Patrick, Hi Patrick, do you mind sharing the information which property you changed solving your problem? Thank you!
... View more
08-10-2019
11:52 AM
Solved Cluster-node users (who obviously execute these actions via rest-api or toolkit cli) had no permission to work with restricted components. Added permission, startet NiFi new and it works. Would by helpfull if somewhere a message would come up to tell that this is an authorization problem...
... View more
08-08-2019
03:50 PM
I have a process-group which has to be started via rest-api. Principial it works to start the process-group but processors inside which are marked as "restricted" won't get started, f.e. ExecuteScript, PutFile. These processors remain stopped. No error message. In nifi-app.log are only the started processors listed. No word of the others. In the UI of course I can start these processors. How to solve this via rest-api? Thanks for any help. Using NiFi 1.9.2 SUPPLEMENT It is not a REST-API thing. Tried with NiFi Toolkit (/bin/cli.sh nifi pg-start -pgid 708358fc-016c-1000-0000-00000bf....). All processors get started excepted the restricted ones. So where is the cause and how to fix this?
... View more
Labels:
- Labels:
-
Apache NiFi
08-07-2019
08:55 AM
@Rosa Negra In this case I would use RouteOnContent to check null and maybe additionally check filesize to be on the safe side.
... View more
08-07-2019
08:46 AM
1 Kudo
Hi @Rosa Negra I only have experience concerning JSON. In my opinion it depends what the content looks like. If the content of an empty JSON is [ ] the flowfile disappears when I do a SplitJson with JsonPath Expression value $. If the content looks like this [ { } ] I check with RouteOnContent on this (^\[\{\}\]) and filter the file out.
... View more
08-05-2019
06:07 AM
@jwitt Sorry uploaded false files nifi-app.log and nifi-bootstrap.log and can't change this anymore. Have a look at NEW_DEV_nifi-app.txt and NEW_DEV_nifi-bootstrap.txt
... View more
08-05-2019
05:39 AM
1 Kudo
I noticed that this subject is discussed on different places. Like recommended from @jwitt I created a thread dump right now because my DEV-System every monday (after 2 days of inactivity) comes up with this data provenance problem. Not only not showing older flowfiles anymore but althoug new created flowfiles don't appear in data provenance.Stopping and restarting NiFi always solves the problem. In the data provenance on the left appears: "Displaying 0 of 0" and even when I change the search options (one day in the past, one day in the future) there will no flowfiles displayed. Please see attached files an let me know if further information can be provided. Thanks! Command for dump used: ./nifi.sh dump emptyDP.log
... View more
08-01-2019
08:35 AM
Once again I have to get max-value of a date. This time an attribute holds the JSON to be checked not the FF-content. This is the content of attribute RESPONSE: [{"id":"(1208)","datbis":"20190630"},{"id":"(1210)","datbis":"20191231"}] With the script of above discussed problem and this information https://gist.github.com/mattyb149/478864017ec70d76f74f (thanks to @Matt Burgess ) it was possible to adjust the script for doing the check in the ff-attribute. Just in case some else has to solve this too here the script: def flowFile = session.get()
if(!flowFile) return
try {
def objList = new groovy.json.JsonSlurper().parseText(flowFile.getAttribute('RESPONSE'))
def max = objList.max {Date.parse("yyyyMMdd",it.datbis)}
flowFile = session.putAttribute(flowFile, 'MAX_datbis', max.datbis.toString())
session.transfer(flowFile, REL_SUCCESS)
} catch(e) {
log.error("Error while determining max", e)
session.transfer(flowFile, REL_FAILURE)
}
... View more
07-29-2019
12:32 PM
1 Kudo
Got it! There was one } missing. Thought if the editor shows the expression coloured it would by syntactical correct. So it has to be: ${RESPONSE:jsonPath('$.[0].id'):equals(${KONTO_BV}):
and(${RESPONSE:jsonPath('$.[0].antauschvon'):le(${now():format("yyyyMMdd")}):
and(${RESPONSE:jsonPath('$.[0].antauschbis'):ge(${now():format("yyyyMMdd")}):
or(
${RESPONSE:jsonPath('$.[0].antauschbis'):isEmpty()})}
)}
)
}
... View more