"how this relates to Cloudera?": there was some lawsuit regarding usage of the code in Intel's ISA-L repository, but I don't know if the patents you mentioned were involved. Intel faced a similar lawsuit, but that was dismissed in 2022 due to an NDA.  I don't know if the Intel lawsuit had any effect on the Cloudera lawsuit. As for PSHUFB patents, most of them are a series of patents filed by William W. Macy, Jr. and others at Intel: https://patents.justia.com/inventor/william-w-macy-jr?page=3 Several of those patents were filed in 2003, but granted in 2010, and 2010 was the first year that Intel included PSHUFB in a processor. Did those patents require an actual hardware implementation before they could be granted? Looking at the patents you linked to, aren't some of those claims essentially duplicates of Intel's patent claims? The point of Intel's ISA-L (Intelligent Storage Acceleration) is to take advantage of instructions that that speed up stuff like CRC (X86 - pclmulqdq) or erasure or error correcting code (X86 - pshufb, vgf2p8affineqb, ...). The most recent activity has been for RISC-V. I worked with LTO tape drives that implemented hardware error correction code on a matrix with a lot of parallel operations, while software was used during development. Some of the software and hardware developers in the tape drive community were doing this stuff back in the mid 1980's. ... View more

@MattWho Apologies for the delay here. I could finally try using certificates with the EKU Extensions and I do not see a similar authentication issue anymore.  Thank you for the kind assistance!  ... View more

Hello @mimei  Thanks for reaching our community.  When you set nifi.web.https.host, that will be the only interface used for login.  If for some reason it does not reply properly or respond as 127.0.0.1, the web UI will never connect. And this looks like it's what is happening in your side:  2025-12-17 13:27:51,877 INFO [main] org.apache.nifi.web.server.JettyServer Started Server on https://vm-P004-4067:8443/nifi 2025-12-17 13:27:51,883 INFO [main] o.a.n.runtime.StandardManagementServer Started Management Server on http://127.0.0.1:52020 As you see, vm-P004-4067 it's answering on 127.0.0.1.  What you can do here is leave nifi.web.https.host empty or specifically set the IP you want to use for the connection.  Also, if you need to change the port, you can this setting: nifi.web.https.port ... View more

@fy-test  Apache NiFi  is only going to be able to address CVEs found in the NiFi-Registry package lib directory files included with the distribution.  Any OS/System-level CVEs would need to be addressed by the owner of the platform on which the NIFi-Registry services is being used. You can find the Apache NiFi Security Reporting here: https://nifi.apache.org/documentation/security/ You'll find CVEs already addressed in NiFi and NiFi-Registry on the above page.  You'll also see how to report any new security vulnerabilities you may discover.   Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

Thanks for responding with a resolution that worked for you, @Pedro_E. I'll mark your response as a solution.  ... View more

Hello Andrés, Yes we had a look at it, in fact it seems it's really solved with 2.7 with https://issues.apache.org/jira/browse/NIFI-14959. I add a look at the code fix provided and well it seems to concern really this partition by attribute. By the way, when we saw this defect, I tried another test. I create a dummy attributs and assign randomly a value 0 - 10 and then tried the partition load by this atrribute. This was even worst than the load balance strategy(I had less reccords processed than the third I had with load balace strategy). If it was the same kind of issue, I was expecting to have roughly the same amount of processed reccords. I say roughly because in this second test I had perhaps 10% of the reccords processed vs 33% with the load balance strategy. In addition, we are not big fans of pushing to our Prod right now a version (2.7.1) which has been released 3 days ago only.  That was why we were searching if someone else faced the issue or if someone else was using this version with load balance strategy without having issue. Just to try to narrow down where the issue comes from: nifi 2.4 or our platform. Anyway thank you very much for your answer Andrés,   Best regards,   Olivier   ... View more

Hello @blackboks,  Thanks for being part of our community.  That error you're facing looks like it's from Java side, not from NiFi.  This appears when no timezone information is provided during the request.  Maybe these two forums can help you find where in your query is missing that:  https://java2blog.com/format-instant-to-string-java/ https://stackoverflow.com/questions/25229124/unsupportedtemporaltypeexception-when-formatting-instant-to-string  ... View more

Hi again @spartakus,  Adding more information, as mentioned, natively, it looks like it's not supported.  But here there is a Jira that explains the behavior and some steps they made:  https://issues.apache.org/jira/browse/NIFI-6152  ... View more

Hello @Isuri, Glad to have you on the community and to hear you're pursuing those certifications.  Congrats on CAISP completion.  That looks like an issue with the platform itself. What I would recommend you is to reach our Certification team via email: certification@cloudera.com They should be able to help you more on that question.  ... View more

Thank you @vafs ! Yes, that made the trick. Thanks; -karsten ... View more