Hi Nathan,
The value of the field can be an Integer or it can be empty. Due to that, I
have configured that field as a nullable field in the schema registry.
When I tried to stamp 0 when the value is null using belo Expression, it
works properly. Hence I believe error is not coming from the
Benji
Probably built on 11 but you're running on 8anyway given we know
now the issue has to do with the json file and you're back in business
it is probably best to leave the debug nar alone.
Thanks Matt for your willingness to help unpack more details. Does
seem like we should do this on
Hi Matt,
Issues with the NAR i assume:
---
2022-08-01 15:30:32,065 INFO [main] org.apache.nifi.nar.NarClassLoaders
Loaded NAR file:
/opt/nifi/nifi-current/./work/nar/extensions/nifi-spring-nar-1.16.0.nar-unpacked
as class loader
Benji,
I've built a custom framework NAR [1] that has additional logging to
identify which components, process groups, etc. are causing the issue.
If you'd like, please feel free to save off your existing framework
NAR and replace it with this, then share the relevant section of the
log (matching
Benji,
Fantastic, thanks for following up! We’ve clearly got something to address but
I’m very happy that we’ve found a way to get you unblocked for now.
Thanks
Mark
Sent from my iPhone
On Aug 1, 2022, at 12:46 PM, BeNJ wrote:
Updates:
Mark: Deleting the json allows nifi to start up(!!) -
Updates:
Mark: Deleting the json allows nifi to start up(!!) - note that restarting
(with the newly generated json in place) causes the same issue on startup.
Joe: I'm happy to run custom debug nars to help figure out how to resolve
this.
Thank you, I really appreciate everyone's help with this!
Agreed with Paul, InvokeHTTP will work without setting an SSLContextService
if the URL you're accessing has a certificate from the generally accepted
certificate authorities like Verisign etc.
I'm a bit late to the party, but I also do not see that the
SSLContextService requires both a key and
I just checked a running NiFi, built locally from the main branch. I
configured an InvokeHTTP processor to perform a GET request to "
https://www.google.com/;. No "SSL Context Service" was configured.
The request completed successfully, routing output to relationships
"RESPONSE" and "ORIGINAL".
Hello
The Apache NiFi team would like to announce the release of Apache NiFi
1.17.0.
This is a feature, improvement, bug fix and security release with 310 JIRAs
completed.
Apache NiFi is an easy to use, powerful, and reliable system to process and
distribute
data. Apache NiFi was made for
Ben
I didn't see any log levels that would help narrow this down. If Mark's
suggestion does not address it it will likely require updating the flow
configuration manually or a patched framework nar to do better logging.
I'm also wondering if the json form of the flow could be imported on a
Benji,
I would recommend you try to remove (or rename) the flow.json.gz - but not the
flow.xml.gz. See if that makes any difference.
Thanks
-Mark
Sent from my iPhone
On Jul 31, 2022, at 11:35 PM, BeNJ wrote:
Also please see the attached nifi.properties
Thanks,
Benji
On Sun, Jul 31, 2022
11 matches
Mail list logo
