I guess my implicit point was that, since you have the ability to reach
into the logging, via /${NIFI_ROOT}///conf/logback.xml/, you could cause
what's logged to be written in place of or in addition to /nifi-app.log/
somewhere else if you desire.
On 8/3/20 2:27 PM, KhajaAsmath Mohammed
Yes errors are being written to log but it would be useful if part of error
was sent as attribute in failure queue. That will help us to decide on what
processor should be called instead of checking logs.
Thanks,
Asmath
On Mon, Aug 3, 2020 at 3:24 PM Russell Bateman
wrote:
> Pardon me, I
Pardon me, I meant: /${NIFI_ROOT}///logs///nifi-app.log ./
On 8/3/20 2:23 PM, Russell Bateman wrote:
Mohammed,
I didn't write /PutSQL/ and I haven't dug around to look at its source
code, but I wouldn't be surprised to learn that those errors were
already written by it to
Mohammed,
I didn't write /PutSQL/ and I haven't dug around to look at its source
code, but I wouldn't be surprised to learn that those errors were
already written by it to /${NIFI_ROOT}/nifi-app.log/ too.
Russ
On 8/3/20 8:56 AM, KhajaAsmath Mohammed wrote:
Hi,
I generally get errors
Hi,
I generally get errors on putsql on the top right for this processor. Is
there a way to get errors inside the attribute so that I can use it and log
in our audit table.
Any other alternative? Put Database gives this attribute but it is not
possible to get with PUTSQL.
Thanks,
Asmath
