Hello, Following up on this, I just wanted to ask if it’s suggested to open an issue.
Thanks G Sent from Proton Mail for iOS On Mon, Jul 25, 2022 at 20:04, Giorgio <g...@protonmail.com> wrote: > Hi Bryan, > > Thank you for getting back to me. Yes, that’s correct we compiled with the > ozone profile. > > G > > Sent from Proton Mail for iOS > > On Mon, Jul 25, 2022 at 18:12, Bryan Bende <bbe...@gmail.com> wrote: > >> Hello, >> >> Did you build your own NiFi off 1.16.1 using the profile >> "include-hadoop-ozone", and then used PutHDFS and that is what >> generated the error in your attached logs? >> >> -Bryan >> >> On Mon, Jul 25, 2022 at 11:08 AM Giorgio <g...@protonmail.com.invalid> wrote: >>> >>> Hello, >>> >>> I would like to report a potential bug that affects NiFi 1.16.1. Our >>> current setup consists of a cluster of 3 nodes and the aim is to build a >>> workflow that can write to both HDFS and Apache Ozone. To this end, we have >>> configured two distinct PutHDFS processors. The configuration of these two >>> processors is such that one points to HDFS and the other one to Ozone using >>> two different core-sites configuration files. The PutHDFS processor that >>> points to Ozone uses OFS as protocol. >>> >>> When we try running the workflow, however, we run into problems. >>> Essentially, this seems to be caused by conflicting libraries that are >>> instantiated by the two processors, thus generating an error. >>> >>> We have found a way to circumvent this problem but this required us to >>> build a custom PutOzone processor that better encapsulates the way the >>> libraries are instantiated. >>> >>> We are not sure whether this is a known issue. Please find attached the >>> relevant log lines. >>> >>> Regards, >>> >>> Giorgio >>> >>> >>> Sent with Proton Mail secure email.
