Connection between RPG and input port is failing via API

Hi, Nifi version 1.5 I am trying to create connection between output port to input port at root RPG. Below is my json request: {"revision": {"clientId": "anonymous","version": 0},"component": {"name": "","source": { "id": "22df69f1-0162-1000--6c01773e", "groupId":

Re: Issues with QueryDatabaseTable processor's State

Marcio, These were choices based on user experience (UX), there's always a tradeoff between ease-of-use and flexibility. We could offer a property for a state prefix (that uses Expression Language), please feel free to write a Jira for that improvement. The original idea was just to specify a

Re: Issues with QueryDatabaseTable processor's State

Matt,  Just curious: Why is it necessary to identify that global state using catalog, schema, table or column names? Those are database concepts. As a user, I'd prefer to have some flexibility here. Surely the component needs to know how to identify the database object, but beyond that, we

Re: Issues with QueryDatabaseTable processor's State

Raman, Originally, we stored state only based on column names, which could obviously cause problems when you have two different tables with the same column name. However this was because the original DB Fetch processors (QueryDatabaseTable, GenerateTableFetch, e.g.) did not accept incoming flow

Issues with QueryDatabaseTable processor's State

Hello Everyone, I am facing an issue with QueryDatabaseTable processor. I have 4 identical mySQL database tables on 4 different AWS instances. The structure is same but data is different. What I am trying to do is, have 4 QueryDatabaseTable processors and fetch the data from all the 4 instances

Re: Error when executing NiFi REST API PUT /processors/{id} call

Hi Vitaly, To give a more detailed example of what Matt is saying, here's the Python version of what you are doing from the NiPyApi test suite. In this test we change the scheduling period of a processor to 3s: processor = nipyapi.canvas.get_processor('someprocessor') update =

Re: NiFi https/ssl configuration

Prashanth, The command you ran to generate client certificates did not have a space between “CN=admin,” and “OU=NIFI” in the certificate DN. This DN must match exactly the Initial Admin Identity you configure in authorizers.xml, which it does not. Either change the IAI to match the certificate

Re: InvokeHttp -- StandardSSLContextService Validator Exception

Pat, That error means that NiFi could not find a valid trusted certificate for the hostname in question within the provided truststore. Understanding that the system in question may be on a limited network, can you please document what “the certs work when I use curl” means? Sometimes people

RE: InvokeHttp -- StandardSSLContextService Validator Exception

The best I could do right now is: invokehttp.java.exception.class javax.net.ssl.SSLHandshakeException invokehttp.java.exception.message sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid

Re: Error when executing NiFi REST API PUT /processors/{id} call

Vitaly, I believe that error is being generated by Jackson which handles the JSON (de)serialization. Often times there is additional information that gets logged to your logs/nifi-user.log. Check there to see if there is anything helpful. By any chance, are you attempting to pass the status back

Error when executing NiFi REST API PUT /processors/{id} call

I am trying to update processors for a workflow, which was previously generated from a template by instantiating it. All work is done from a Java program through NiFi REST API. Template holds processors in a group. Since I know the template group name and strategy by which NiFi assigns a new

Re: Reuse of templates and formatting functions

Thanks Bryan. That helps. We were also thinking of exposing standard formatting functions as an API that other data flows can call and use. Regards Anil On Tue, Mar 13, 2018 at 1:13 PM, Bryan Bende wrote: > Anil, > > It sounds like what you are interested in would be some

Re: Reuse of templates and formatting functions

Anil, It sounds like what you are interested in would be some combination of the referenceable process groups [1] or worm-hole connections [2], which were ideas that were discussed, but haven't been implemented. You might be able to make your situation slightly better by using the NiFi Registry

Reuse of templates and formatting functions

Team, My question is around re-use. Templates : We are creating flows for different use cases. Most of them have a requirement for retry. Say the API call fails, we would like to retry 3 time after certain interval before giving up. We have created a retry template that works perfect. Q: If I

RE: InvokeHttp -- StandardSSLContextService Validator Exception

The working example looks the same as mine. I’ll post a trace when I get to that computer. Pat From: Jorge Machado [mailto:jom...@me.com] Sent: Tuesday, March 13, 2018 9:48 AM To: users@nifi.apache.org Subject: Re: InvokeHttp -- StandardSSLContextService Validator Exception Any trace for us

Re: InvokeHttp -- StandardSSLContextService Validator Exception

Any trace for us ? Working Example: Jorge Machado > On 13 Mar 2018, at 13:11, Jones, Patrick L. wrote: > > Howdy, > > I’m using a StandardSSLContextService with InvokeHttp and I get a > ValidatorException ‘unable to find valid certification path to requested >

RE: NiFi https/ssl configuration

Hi Team, I did the following steps to configure ssl for nifi: * Ran `bin/tls-toolkit.sh standalone -n 'hostname' -C 'CN=admin,OU=NIFI' -o ./target` * Copied nifi.propeties, keystore & trustore jks file under nifi/conf folder * Updated authorizers.xml with

InvokeHttp -- StandardSSLContextService Validator Exception

Howdy, I'm using a StandardSSLContextService with InvokeHttp and I get a ValidatorException 'unable to find valid certification path to requested target.' The certs work when I use curl. I put the CA cert and the public key cert in the StandardSSLContextService truststore and the private