Re: nifi questions

Thank you for very helpful feedback. On Wed, Jul 5, 2017 at 1:46 PM, Joe Witt wrote: > ah! Good call Mike and thanks for adding that. > > On Wed, Jul 5, 2017 at 2:21 PM, Michael Hogue > wrote: > > Clay, > > > > Regarding number one, Joe is

Re: Filesystem based Schema Registry, does it make sense?

Joe, At least in my case, I would be happy to control versioning outside nifi (eg via git). I would suspect that by adopting an approach like this versioning would be handled pretty much like the AvroSchemaRegistry? I assumed that with AvroSchemaRegistry you either name your schema with

UI Not Responsive

All, I am currently running NiFi 1.2.0 on a Linux(RHEL) machine. Everything was running fine until yesterday where it started behaving weird. The UI is not at all responsive and sometimes the page wouldn't even load. I bumped up the Java Heap Space just to make sure I'm not overloading the

Re: evaluateJsonPath processor

Hi Matt, Thanks. ³$" works well. On 7/5/17, 4:09 PM, "Matt Burgess" wrote: >Yuri, > >If your Return Type is set to "json" then you should be able to use >"$" as the JSON Path rather than "$." > >Also to put the entire content into an attribute you could use >ExtractText

Re: evaluateJsonPath processor

Yuri, If your Return Type is set to "json" then you should be able to use "$" as the JSON Path rather than "$." Also to put the entire content into an attribute you could use ExtractText to match the entire body, this works whether the file is JSON or not. Regards, Matt On Wed, Jul 5, 2017 at

evaluateJsonPath processor

Hello Everyone, Could anyone please advise why $. expression is considered invalid in EvaluateJsonPath processor. The idea is to copy the entire content of a JSON-formatted flowfile into its attribute. Thanks, Yuri LEGAL DISCLAIMER: M.C. Dean, Inc. and its

Re: Custom NAR interfering with BundleUtils.findBundleForType

To provide closure to this thread: Bryan, the exception indeed was being thrown there, but the root cause of that was because "Ghost" processors were being created in the place of the actual processors because my custom NAR was confusing BuildUtils.findBundleForType. Joe, thank you very

Re: MiNiFi & SSL Context

Marc Thanks for the reply, yes, I tried sending from MiNiFi to NiFi using a http post (using usename/password). In opetations I would need to use ssl, but I know in NiFi the sslcontext is setup in the UI and stored in the flow.xml.gz file. As I created my flow in NiFi and then templated it

Re: nifi questions

ah! Good call Mike and thanks for adding that. On Wed, Jul 5, 2017 at 2:21 PM, Michael Hogue wrote: > Clay, > > Regarding number one, Joe is correct. There current isn't a processor that > can process arbitrary protobuf messages, but InvokeGRPC and ListenGRPC were

Re: nifi questions

Clay, Regarding number one, Joe is correct. There current isn't a processor that can process arbitrary protobuf messages, but InvokeGRPC and ListenGRPC were recently added (targeting 1.4.0) that can accept and send gRPC messages (which wrap protobuf) defined by an IDL [1]. There's a how-to

Re: Custom NAR interfering with BundleUtils.findBundleForType

Scott, Thanks for providing the stacktrace... do any of your custom processors use the @DefaultSchedule annotation? and if so, do any of them set the tasks to a number less than 1? The exception you are getting is from some code that is preventing using 0 or negative number of tasks for a

Re: Communication between flows

Steve, In 1.2.0 there were some new processors added called Wait/Notify... With those you could send your original JSON (before splitting) to a Wait processor and tell it to wait until the signal count is equal to the number of splits, then you could put a Notify processor right after PutMongo

Communication between flows

Is there a mechanism or technique for communicating the results of a flow file to its "sister" flow files? Here is a high-level description of what I am doing: Input to my flow is a JSON array of documents that get split (SplitJson) into individual documents and each document becomes a

Re: Custom NAR interfering with BundleUtils.findBundleForType

Hi Joe, We are extending AbstractProcessor for our processors, and AbstractControllerService for our controller service. However, we did include the InvokeHTTP processor with some modifications that are referencing some other classes that are in the nifi-processors-standard JAR. I will

Re: MiNiFi & SSL Context

Hello David, I'm making the assumption here that you are attempting to use an SSLContextService within a consumable suck as InvokeHTTP: The configuration for MiNiFi Java will be very similar to that of NiFi. The System guide [1] for MiNiFi references the NiFi System administration guide's

Re: Filesystem based Schema Registry, does it make sense?

I think it does make sense and someone at a meetup asked a similar question. There are some things to be considered like how does one annotate the version of a schema, the name, etc.. when all they are providing are files in a directory? How can they support multiple versions of a given schema

Re: Custom NAR interfering with BundleUtils.findBundleForType

Scott In your custom NAR are you extending some other processor/component such as one found in standard processors? You'll really need to break that chain and not pull in the same components. Can you share the actual error being provided at startup/ Thanks joe On Wed, Jul 5, 2017 at 11:53 AM,

Custom NAR interfering with BundleUtils.findBundleForType

Hey all, I have been running on NiFi 1.1.1 for a while, and just started working on migrating to 1.3.0. However, when I tried starting up, I was getting unhandled exceptions during startup of Jetty. I have traced this down to something being wrong with a custom NAR file that we built

Filesystem based Schema Registry, does it make sense?

dev, As I continue to explore the Record based processors I got myself wondering: Does it make sense to have a file-system based schema registry? Idea would be creating something like AvroSchemaRegistry but instead of the adding each schema as a controller service property, we would have a