Re: PUT/flow/process-groups/{id} API

2018-04-06 Thread Bryan Bende
I'm not sure if this is helpful to compare to what you are trying to do, but in the CLI that is soon to be released with 1.6.0, we have a similar command for "pg-start". Here is how it is implemented:

RE: PUT/flow/process-groups/{id} API

2018-04-06 Thread Vitaly Krivoy
Thank you for replying Matt. It’s not secured. Not yet. I am still in the early stages of developing a prototype. The PUT/flow/process-groups/{id} API description says that the Components object is optional and if one is not provided, all processing group components will be started. Until now

RE: PUT/flow/process-groups/{id} API

2018-04-06 Thread Vitaly Krivoy
As soon as I added components object, it worked. And in a retrospect it makes sense, because you want to identify the client for locking. In current state NiFi, the API documentation is a developer's worth enemy, but those who overcome this hurdle, will understand NiFi pretty well. Thank you

Re: processGroupId URL

2018-04-06 Thread scott
Hi Matt, No, I'm looking for the main UI URL, like so: http://localhost:8899/nifi/?processGroupId=9e338e2f-0162-1000-969a-043d35e4c41d= I'm using NiFi 1.5. What I'd really like is some way to know, using a variable or attribute, that the processor which caused the error resides within

Re: NiFi 1.6

2018-04-06 Thread Jorge Machado
Voting is taking now place from RC3. Probably in the next two weeks. Jorge > On 5 Apr 2018, at 22:46, dan young wrote: > > any updates on when 1.6 is going to drop? > > dano >

RE: NiFi 1.6

2018-04-06 Thread Mohit
Joe, What is the expected date? From: Joe Witt Sent: 06 April 2018 02:20 To: users@nifi.apache.org Subject: Re: NiFi 1.6 dan It is presently working through the release candidate vote process. As it stands now it could be out tomorrow. Please do help by

Re: NiFi 1.6

2018-04-06 Thread Pierre Villard
As Joe said: the vote is ongoing and remains opened 72h. Unless there is an issue reported in the next 24h, NiFi 1.6 should be out this WE. Pierre 2018-04-06 11:47 GMT+02:00 Mohit : > Joe, > > What is the expected date? > > > > *From:* Joe Witt

RE: MiNiFi C++ and Tensorflow future plans?

2018-04-06 Thread Mendez Veiga, Iyan
Thanks for you quick answer Andy! Unfortunately, I cannot share any information about the use cases (company policy) for the moment but, of course, if we publish something in the future, I will be glad to share our feedback with the community. Looking forward to this 1.0 release. Best

RE: PUT/flow/process-groups/{id} API

2018-04-06 Thread Vitaly Krivoy
When I start a group from NiFi UI and I examine the request in Chrome Developers Tools, it is identical to the one that I send from a Java program. What gives? From: Vitaly Krivoy [mailto:vitaly_kri...@jhancock.com] Sent: Thursday, April 05, 2018 5:49 PM To: users@nifi.apache.org Subject:

Re: processGroupId URL

2018-04-06 Thread Matt Gilman
Scott, What version of NiFi are you running? If your running NiFi 1.x then the parent process group ID shouldn't be necessary. The fully qualified URL of a processor would look something like http://localhost:8080/nifi-api/processors/9b52d2bf-0162-1000-d1ac-89e944aa1bfe Or are you trying to

Re: PutDatabaseRecord won't put Timestamp field

2018-04-06 Thread Matt Burgess
Mike, Yeah I was using 1.6 (master) but I'm not aware of any changes between the two versions that would affect that. It looks like in your version when record.getValues() is called, it is not converting the logical Avro type of "timestamp" into a Timestamp and is instead just interpreting it as

Re: PUT/flow/process-groups/{id} API

2018-04-06 Thread Matt Gilman
Vitaly, That endpoint will start/stop every component the requesting user has access to. Is your instance secured? If so please ensure that your including necessary authentication details. For instance, if your using client certificate in your browser be sure you request in your Java program