Re: NiFi 1.4 Clustering Error: Cannot Replicate Request GET /nifi-api/flow/current-user

Ryan, I remember creating an issue for something that seems similar to what you are running into: https://issues.apache.org/jira/browse/NIFI-3642 Long story short, I believe you do need to specify a value for nifi.web.http.host because that will be used to replicate requests that come in to the

Re: NiFi 1.4 Clustering Error: Cannot Replicate Request GET /nifi-api/flow/current-user

sues.apache.org/jira/browse/NIFI-3642 since jetty can't bind to a > VIP. > > -Ryan H > > On Mon, Jan 29, 2018 at 12:28 PM, Bryan Bende <bbe...@gmail.com> wrote: >> >> Ryan, >> >> I remember creating an issue for something that seems similar to what >>

Re: PublishKafka setting record timestamp

> > I guess, I will open an enhancement request then. > > Mika> > > > > On 01/30/2018 02:58 PM, Bryan Bende wrote: >> >> Hello, >> >> The timestamp in Kafka is separate from the headers, currently there >> isn't a way to specify the timestamp from N

Re: NiFi Registry Create Item in the UI

Andrew, I agree it is a little confusing, especially when you first enter a brand new registry instance with no data. However, the main page of the registry is not a listing of buckets, it is a listing of "items" across all buckets, where currently the only time of item is a flow. You then click

Re: Deployment of Flow Files help

Hi Sean, Are you using NiFi Registry [1]? That should be your primary way of deploying flows. I'm assuming you are asking how you can automate this so that you can spin up a new cluster and then deploy a flow automatically, is that correct? If you are not talking about automation, then

Re: Deployment of Flow Files help

to deploy from our CI/CD server. > > > The final plan is to move NiFi into a scalable Kubernetes cluster with > automated deployment of flow files. > > On 15 February 2018 at 4:56:04 pm, Bryan Bende (bbe...@gmail.com) wrote: > > Hi Sean, > > Are you using NiFi Registry [

Re: Registry, sdlc and promotion between environments

Georg, In addition to what Joe and Andrew mentioned, it really comes down to how you want to setup your environment... In a simple scenario, there would be multiple NiFi instances and a shared registry instance. In one of the NiFi instances you build a flow, start version control, and save v1 to

Re: Secure NiFi Cluster Unable to Obtain Buckets from Secure NiFi Registry

Ryan, Did you happen to enter the registry client in NiFI using the IP address of the registry? I'm not totally sure, but based on that message it seems like its trying to connect to an IP address, but the certificate of the registry only contains the hostname of the registry. -Bryan On Wed,

Re: NiFi Clustering

Hello, Each node must have its own repositories, you can't point multiple nodes at the same repositories. The repositories for a given node could be on local disk, or on a mounted network drive, but local disk will likely have the best performance. Thanks, Bryan On Wed, Dec 20, 2017 at 1:25

Re: [EXT] Re: NiFi Clustering

> > Thanks for your response , We are going with individual repositories. Can > you explain what are the cons of having a shared content repository between > multiple nodes ? I may be asking a dumb question but we are trying to > understand if shared filers increase the throughput of th

Re: Nifi REST API access to OpenID connect secured instance

Chris, I only have a high-level understanding of how OIDC authentication works, and I am not exactly sure how to simulate this via curl, but here is what I think is happening... There are three REST end-points in NiFi... - /access/oidc/request - /access/oidc/callback - /access/oidc/exchange

Re: Separating custom service API from its implementation

Tim, In the case where it is your own custom service api and service impl, and you know you are never going to have another implementation of the API, then it doesn't really matter and having them all in one NAR will work. The issue is that by bundling the implementation with the API, now

Re: Simple CSV to Parquet without Hadoop

gt;>> > >>> > Failed to locate the winutils binary in the hadoop binary path >>> > IOException: Could not locate executable null\bin\winutils.exe in the >>> > Hadoop >>> > binaries >>> > Unable to load native-h

Re: Simple CSV to Parquet without Hadoop

Scott, Unfortunately the Parquet API itself is tied to the Hadoop Filesystem object which is why NiFi can't read and write Parquet directly to flow files (i.e. they don't provide a way to read/write to/from Java input and output streams). The best you can do is trick the Hadoop API into using

Re: Simple CSV to Parquet without Hadoop

or scheme > > BTW, I'm using NiFi version 1.5 > > Thanks, > Scott > > > On Tue, Aug 14, 2018 at 12:44 PM, Bryan Bende wrote: >> >> Scott, >> >> Unfortunately the Parquet API itself is tied to the Hadoop Filesystem >> object which is why NiF

Re: AVRO is the only output format with ExecuteSQL

I would also add that the pattern of splitting to 1 record per flow file was common before the record processors existed, and generally this can/should be avoided now in favor of processing/manipulating records in place, and keeping them together in large batches. On Tue, Aug 7, 2018 at 9:10

Re: configuration variables?

The variable registry is hierarchical, so variables defined in a parent group will be visible to all children, unless a child group has a variable with the same name which will override the parent's value. So you can put any common variables in the root group. On Tue, Aug 7, 2018 at 9:40 AM, l

Re: Multiple registry instances sharing Git repo

Mike, It is not really made to have multiple instances pointing at the same git repo. Each registry has a metadata DB and a flow storage component which can be filesystem or git. So the metadata DB won't know about the stuff created in the other instance. Generally it is either a single shared

Re: [EXT] Re: Get all Processors

You could probably achieve the same thing but traversing the process groups and asking each one for its processors without the includeDescendantGroups=true. It would be more complex on the client side, but would avoid making one huge request. On Tue, Aug 14, 2018 at 11:07 AM, Karthik Kothareddy

Re: ConvertAvroSchema with unmapped fields

Have you tried using ConvertRecord instead of ConvertAvroSchema? ConvertAvroSchema comes from the Kite bundle which has a few other processors like ConvertCsvToAvro and ConvertJsonToAvro, all of which existed before NiFi's record processing capabilities. In general the record processors should

Re: Managing Secrets in NiFi Registry

Hello, You are correct that currently variables cannot be marked as sensitive, and for that reason they currently shouldn't be used to store sensitive values since they will be stored in plain-text in the flow.xml.gz and also in the versioned flows saved to registry. I do think the concept of

Re: Nifi Publish/Consumer Kafka and Azure Event Hub

Hello, Any user defined properties in the processor should be passed along to Kafka so you should be able to add a new property with the name sasl.mechanism and the value PLAIN, without that the processors will assume GSSAPI. On Wed, Sep 5, 2018 at 9:55 PM João Henrique Freitas wrote: > > Hi

Re: NiFi ExecuteScript vs multiple processors vs custom processor

Boris, Regarding templates being limited... templates were really made as a way to share example flows, or help with debugging if you need to send someone your flow. Unfortunately they turned into a deployment mechanism since there wasn't a better solution at the time. Using NiFi Registry should

Re: NiFi ExecuteScript vs multiple processors vs custom processor

ink with registry 0.1 it was > not possible to version nested PGs within parent PGs so I could not have > "templatized" PG which has it is own version and use that PG with other > versioned PGs. Has it changed with registry 0.2 now out? > > On Tue, Jul 10, 2018 at 11:08 AM Bry

Re: Nifi Registry + Git: target registry ignores git flows

Assuming you have a dev DB & git repo and then a prod DB & git repo, each DB goes with the corresponding repo and has ids that are unique to the environment, so you can't take one of the DBs and point at the other’s git repo, that is why you need the export/import process with the CLI. The

Re: Invoke HTTP custom headers.

Hello, The "Attributes to Send" property is a regular expression, so you should be able to put ".*" to send all flow file attributes as headers, or you can make a pattern that matches a group of attributes that follow some naming convention. Thanks, Bryan On Mon, Sep 10, 2018 at 6:22 AM,

Re: NiFi retry capabilities

Boris, "Penalty Duration" is per flow file, and "Yield" is for the processor. If the processor penalizes a flow file and transfers it to a queue, whatever is processing that queue won't take that flow file from the queue until the penalty duration has passed. If a processor yields, then the

Re: Extract primary node hostname/ipaddress in the flow

Hello, There is a hostname() function in EL, but there is not one specifically for the primary node. I think this has come up before and probably makes sense, it just hasn't been implemented yet. -Bryan On Thu, Mar 1, 2018 at 9:28 AM, ashmeet kandhari wrote: > Hi

Re: Atlas and NiFi integration help

be used to answer > these questions. > > Thanks, > > Mike > > On Thu, Mar 1, 2018 at 10:20 AM, Bryan Bende <bbe...@gmail.com> wrote: >> >> Mike, >> >> As far as I know, Atlas is not really about "event level" lineage, it >> is more about &q

Re: Atlas and NiFi integration help

Mike, As far as I know, Atlas is not really about "event level" lineage, it is more about "system level" or "data set' level. So I believe the goal of Atlas is to show how the systems are connected and how a particular data set flows through the system. So an example might be... NiFi pulls from

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

Re: Killing 'Stuck' Processors without restarting NiFi

Can you provide the portion of the thread dump for one of the stuck threads so we can see where it is getting stuck? This really shouldn't be normal occurrence. On Tue, Apr 3, 2018 at 12:10 AM, Pierre Villard wrote: > On my phone right now, can't provide much

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

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: Ranger-plugin authorises "anonymous" for /flow

solution. > > [1] > https://community.hortonworks.com/questions/142667/how-to-give-permissions-to-users-to-access-nifi-ui.html > > On Mon, Apr 9, 2018 at 4:09 PM, Bryan Bende <bbe...@gmail.com> wrote: >> >> Ah thanks for the info, didn't know that. >> >>

Re: Ranger-plugin authorises "anonymous" for /flow

lse the authorizer would check if the incoming identity is "anonymous" and reject the request before even checking the actual policies from Ranger. On Mon, Apr 9, 2018 at 11:10 AM, Bryan Bende <bbe...@gmail.com> wrote: > Ok, so you end up in the NiFi UI with the identity in t

Re: Ranger-plugin authorises "anonymous" for /flow

s >>"anonymous" and reject the request before even checking the actual >>policies from Ranger. > > Would this be a good setting to have in general, perhaps for managed > authorizer or in nifi.properties, so that it could be toggled for any > configured a

Re: Ranger-plugin authorises "anonymous" for /flow

name+variable > > which is used by certain matcher classes. > > On Mon, Apr 9, 2018 at 3:28 PM, Bryan Bende <bbe...@gmail.com> wrote: >> >> Hello, >> >> I don't see any issue with the code you linked to. It's saying "if the >> ranger policies say

Re: Ranger-plugin authorises "anonymous" for /flow

Hello, I don't see any issue with the code you linked to. It's saying "if the ranger policies say the operation is allowed, then return approved". Is '{USER}' a special syntax in Ranger? or are you using that as a placeholder in email so you don't have to provide the real user identity? I

Re: Cluster coordinator does not update cluster subdomain when new node states up

Did you rebuild all your ZooKeeper servers too, or just rebuilt NiFi servers point at the same existing ZooKeeper? On Thu, Apr 5, 2018 at 2:16 PM, Andy LoPresto wrote: > I suppose it could be a weird routing issue with your DNS settings or a > modified /etc/hosts file? Can

Re: Security issue when programmatically trying to create DBCP Controller Service

There should be an exception in nifi-app.log for the message you received: "Unable to create component to verify if it references any Controller Services" If you can find the stacktrace for that exception in nifi-app.log and provide it here, it may be helpful to see what is going on. On Fri,

Re: Referencing a property from nifi.properties into a processor.

You can also set system properties in bootstrap.conf, this was the primary way of setting up variables before either of the variable registries existed. java.arg.123=-Dmyvar=myvalue On Thu, Apr 19, 2018 at 8:41 AM, Matt Burgess wrote: > If you are using a version of NiFi

Re: Getting Untrusted Proxy when logging into cluster

Standalone mode does not need the proxy permission so it is likely that the certificate of the standalone node also has the double-quotes, but it just doesn't matter. If you use keytool to list the contents of the keystore.jks, does it show the Owner with the double quotes? keytool --list -v

Re: NIfi and Nifi Registry Connection Error

hBuilder.build(SunCertPathBuilder.java:141) > at > sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126) > at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280) > at > sun.security.validator.PKIXValidator.doBu

Re: NIfi and Nifi Registry Connection Error

Ok, can you provide the stacktrace from nifi-app.log when it gets the socket timeout? On Wed, Mar 28, 2018 at 3:45 PM, Scott Howell <scotthow...@mobilgov.com> wrote: > Yes I have https: defined on the registry client. > >> On Mar 28, 2018, at 2:29 PM, Bryan Bende <bb

Re: NIfi and Nifi Registry Connection Error

Just to double-check, when you defined the Registry Client in NiFi, did you enter the URL starting with "https" ? On Wed, Mar 28, 2018 at 3:13 PM, Scott Howell wrote: > I have a single node nifi server setup with a self-signed keystone and > truststore. I then used the

Re: PutHDFS with mapr

If you want to see the classpath of a processor that has an "Additional Resources" property, you should be able to turn on TRACE logging for ExtensionManager in logback.xml: Wait 30 seconds, then modify the value of the "Additional Resources" property to force it to print. It will only print

Re: Processor example with dynamically fetched values for attributs

ush" mode). > > -- otherwise, the UI would have to call the NiFi server for refresh, from > time to time. > > Thanks. > > Regards, > Dominique > > > > 2018-03-26 17:59 GMT+02:00 Bryan Bende <bbe...@gmail.com>: >> >> Hello, >> >> This pat

Re: Processor example with dynamically fetched values for attributs

Hello, This pattern isn't really supported at the moment... You would not want to make calls to external services when opening the config window of a processor because then you risk blocking on an network call if the system is down or unresponsive, or just risking taking a really long time to

Re: Store Hash data type in redis

If you setup the RedisDistributedMapCacheClient, you can then use the PutDistributedMapCache processor to store anything you want in Redis. You could use the HashContent processor and then store that in Redis. -Bryan On Fri, Mar 23, 2018 at 9:03 AM, Mike Thomsen wrote:

Re: HDFS Processors and Native Compression Codecs

Shawn, You are right, the issue is that the JVM only allows a native library to be loaded once, and furthermore if you have native methods that need to be linked to the native library, the native code must be in the same class loader where the native library is loaded (at least from my testing).

Re: Nifi processor stops picking up file from queue

Hello, Approximately how many flow files are generated by the split? -Bryan On Mon, Mar 26, 2018 at 4:26 PM, af6140 wrote: > This is nifi 1.2.0. > > > > -- > Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/

Re: Issue with AWS ELB on secure nifi-registry

main and port I can access the UI but >> nothing else after that. >> >>3. When I am on an instances in the same private subnet I am able to curl >> to the instance I get the TLS SSL which tells me the keystore is on the >> server. I am using a JKS keystore th

Re: Issue with AWS ELB on secure nifi-registry

Hello, What error are you getting when you cannot access the UI? Is there anything interesting in nifi-registry-app.log regarding authentication/authorization when this happens? Can you access the UI securely without going through the ELB? Thanks, Bryan On Mon, Mar 19, 2018 at 10:05 AM,

Re: Issue with AWS ELB on secure nifi-registry

" action="R"> > > > resource="/tenants" action="W"> > > > resource="/policies" action="R"> > > > resource="/policies&q

Re: GG kafka topic in avro format to NiFi

Hello, You don’t need to use a properties file. In your AvroRecordReader, just change the Schema Name property from ${schema.name} to the actual name of the schema you want to use from the schema registry. It just means that the record reader can only be used with one schema now, rather than

Re: put pictures from remote server into hdfs

Hello, It would probably be best to use GetSFTP -> PutHDFS. No need to write the files out to local disk somewhere else with PutFile, they can go straight to HDFS. The filename in HDFS will be the "filename" attribute of the flow file, which GetSFTP should be setting to the filename it picked

Re: Issue with AWS ELB on secure nifi-registry

gov.com> wrote: >>> >>> Thanks for the quick response. >>> >>> A couple of things I am seeing. >>> >>> 1. There is no error, I don’t see anything in the logs once the service >>> comes up. This is because the health check is not e

Re: Issue with AWS ELB on secure nifi-registry

n.file.FileUserGroupProvider > conf/users.xml > > Provider">file-user-group-provider > conf/authorizations.xml > > > > > managed-authorizer > > org.apache.nifi.registry.security.authorization.St

Re: Issue with AWS ELB on secure nifi-registry

The base file is here for comparison: https://github.com/apache/nifi-registry/blob/master/nifi-registry-resources/src/main/resources/conf/identity-providers.xml#L23 On Mon, Mar 19, 2018 at 5:34 PM, Bryan Bende <bbe...@gmail.com> wrote: > For your first file, is what you showed there

Re: Issue with AWS ELB on secure nifi-registry

resource="/policies" action="R"> > > > resource="/policies" action="W"> > > > resource="/controller" action="R"> > >

Re: Issue with AWS ELB on secure nifi-registry

edacted}, O={redacted}, L=Kansas City, >> ST=Missouri, C=US >> >> Is there an issue with using a wildcard cert? >> >> >>> On Mar 21, 2018, at 10:23 AM, Bryan Bende <bbe...@gmail.com> wrote: >>> >>> All identity strings are case & whitesp

Re: Issue with AWS ELB on secure nifi-registry

gt; nifi.cluster.node.protocol.port= > nifi.cluster.node.protocol.threads=10 > nifi.cluster.node.event.history.size=25 > nifi.cluster.node.connection.timeout=5 sec > nifi.cluster.node.read.timeout=5 sec > nifi.cluster.firewall.file= > > > # zookeeper properties, used for clus

Re: Issue with AWS ELB on secure nifi-registry

uri, C=US > > > > I made the CN=*.{redacted}.com just like the self-signed certificate showed. > I now have a 1 node cluster up and running. It seems like NIfi isn’t taking > into account the wildcard and treating it as a “*” instead. > >> On Mar 21, 2018, at 11:33 A

Re: NiFI Maven Plugin - Timestamped Snapshot Version Problem

Hi Arne, Thanks for the detailed explanation, that is an interesting scenario, but I can see why it would be problematic. Can you file a NiFi JIRA with that write up and tag the component as "Nar-Maven-Plugin" ? Thanks, Bryan On Fri, Mar 2, 2018 at 12:02 PM, Arne Degenring

Re: Why is a DistributedMapCacheServer started on every NiFi instance?

Hello, In the older 0.x line of NiFi there was a way to target a controller service to the NCM or to nodes, so you would have chosen NCM in this case. In the 1.x line the NCM was removed and as a result a controller service can only be started on all nodes. We should probably consider allowing a

Re: NiFi in cluster mode

Hello, 1) Currently remote ports still need to be on the root canvas. 2) Hard to say the limit, but you will be bound the number of TCP connections you can create and how many threads can handle them. 3) You could still use process groups to enclose the flow of the template, and inside the

Re: setting processor concurrency based on the development/production environment

Hello, Glad you are having success with NiFi + NiFi Registry! You brought up an interesting point about the concurrent tasks... I think we may want to consider making the concurrent tasks work similar to variables, in that we capture the concurrent tasks that the flow was developed with and

Re: FetchParquet Type Conversion Error

Joe, There was a similar issue I worked on recently that had to do with array handling: https://issues.apache.org/jira/browse/NIFI-5316 From a quick glance this may be a different variation of a similar issue. We are using Parquet’s Java API

Re: Registry - deleting versions of flow

I think we need to implement what you described in option #2 which is basically like a force push in git terminology. If you want to create a JIRA for that I think it is a good request. > On Jun 29, 2018, at 6:40 AM, Fredrik Skolmli wrote: > > Hi everyone. > > I'm not sure if my workflow

Re: putsolrcontentstream and kerberos

I've only done it against Solr cloud, but I don't know a reason why it wouldn't work against standalone Solr. Nothing is jumping out at me as being wrong with your config. My JAAS config was the following: SolrJClient { com.sun.security.auth.module.Krb5LoginModule required useKeyTab=true

Re: Delay a FlowFile for a specific amount of time

Maybe a Wait processor with an expiration of 60 mins? If you never use a Notify processor then its basically just going to wait til the expiration. On Mon, Oct 15, 2018 at 4:10 PM Peter Wicks (pwicks) wrote: > > A coworker and I were working on a problem where we needed to delay a group > of

Re: Issue with RouteOnAttribute

Hello, You cannot reference flow file content from expression language, so whatever you want to route on will need to be extracted into a flow file attribute. You can use EvaluateJsonPath with something like status = $.result.status then in RouteOnAttribute ${status:equals('OK')} Thanks,

Re: NiFi fails on cluster nodes

The cluster configuration section of the admin guide [1] is independent of whether it is embedded or external zookeeper. The only real difference is you won't set nifi.state.management.embedded.zookeeper.start=true, but besides that you all of the other config would be the same whether using

Re: NiFi fails on cluster nodes

This is not related to ZooKeeper... I think you are missing something related to TLS/SSL configuration, maybe you set cluster protocol to be secure, but then you didn't configure NiFi with a keystore/truststore? On Mon, Oct 15, 2018 at 9:41 AM Mike Thomsen wrote: > > Not sure what's going on

Re: NiFi fails on cluster nodes

is set to 'true', since otherwise, > NiFi would require values for 'nifi.web.http.host' and 'nifi.web.http.port'. > We have a cert that is used to serve HTTPS requests to the NiFi web UI, and > it works just fine. > > -Original Message- > From: Bryan Bende > Sent: Monda

Re: FetchFile Completion Strategy

: > > Took a look at the pull request and that should handle the issue I was > seeing. Is there going to be an issue with the directory being left there if > something else fails? For my case the empty directory is fine. > > > Thanks > > Shawn Weeks > > _

Re: FetchFile Completion Strategy

Hi Shawn, The way the processor works is the following... 1) Perform checks to try and ensure the completion strategy will work later 2) Perform the fetch and if successful then transfer to success and commit the session 3) Perform the completion strategy The issue is if the completion fails in

Re: question about ConsumeKafka metrics for incoming data

Hello, Bytes in is the # of bytes read from incoming flow files. Since source processors don't have incoming flow files they will never have bytes in or flow files in. -Bryan On Thu, Oct 18, 2018 at 11:25 AM Dominique De Vito wrote: > > Hi, > > While running a ConsumeKafka processor, I noticed

Re: NiFi fails on cluster nodes

at > org.springframework.expression.spel.ast.MethodReference.getValueInternal(MethodReference.java:129) > > at > org.springframework.expression.spel.ast.MethodReference.access$000(MethodReference.java:49) > > at > org.springframework.expression.spel.ast.

Re: NiFi fails on cluster nodes

w authorizers.xml? I’m asking > since we have the same LDAP authentication/authorization settings in the > latter. > > > > Thank you, > > > > Alexander > > > > -Original Message- > From: Bryan Bende > Sent: Monday, October 22, 2018 11:55 AM > To

Re: Processor not found on loading template. But exists in the AddProcessor menu.

t; > > > Thanks Bryan. I will take a look now. Regarding nifi-app.log, I will > > look for it. Wasn't sure if I had to configure something for the > > binary version to write the log, or set it's verbosity. > > On Fri, Oct 19, 2018 at 12:27 PM Bryan Bende wrot

Re: NiFi fails on cluster nodes

we will need to re-create all users and > groups that we had in the original standalone NiFi instance? > > -Original Message- > From: Bryan Bende > Sent: Monday, October 22, 2018 12:48 PM > To: users@nifi.apache.org > Subject: Re: NiFi fails on cluster nodes > >

Re: Processor not found on loading template. But exists in the AddProcessor menu.

Can you look in the template using a text editor and find the element for the processor you are referring to, and look for the "bundle" elements and see if the bundle info (group, artifact, version) in the template matches the info for the processor in the UI? Also would be helpful to see the

Re: [EXTERNAL] Re: putsolrcontentstream and kerberos

st out of curiosity, what version of java are you > running? Does anyone know which version of SolrJ is using the the 1.6 > putsolrcontentstream? > > -Original Message----- > From: Bryan Bende [mailto:bbe...@gmail.com] > Sent: Friday, October 12, 2018 2:08 PM > To: user

Re: [External] Re: Issue with RouteOnAttribute

What is the syntax issue connecting EvaluateJsonPath to RouteOnAttribute ? On Mon, Oct 15, 2018 at 1:21 PM N, Vyshali wrote: > > Hi, > > > > I’m not appending the “status” attribute to the input json content. I’m just > using as a parameter for comparison > > I tried the same way connecting

Re: [EXTERNAL] Re: Re: putsolrcontentstream and kerberos

; or upgrade SolrJ to 6.6. > > I just tried the flow on the Lab systems running Nifi 1.7 and Kerberos > authentication worked. Looks like we are going to be doing an upgrade. > > > -Original Message- > From: Bryan Bende [mailto:bbe...@gmail.com] > Sent: Monday, O

Re: NiFi Toolkit CLI issues with NiFi/Registry SSL handshake

So you're saying the CLI properties for the keystore and truststore match exactly what is in your nifi.properties for the nifi.security properties? Basically these should be identical... nifi.properties nifi.security.keystore= nifi.security.keystoreType= nifi.security.keystorePasswd=

Re: NiFi fails on cluster nodes

ou anything. > > > > BTW, what does “a different location in the same ZK” mean? > > > > -Original Message- > From: Bryan Bende > Sent: Tuesday, October 23, 2018 3:02 PM > To: users@nifi.apache.org > Subject: Re: NiFi fails on cluster nodes > &g

Re: NiFi fails on cluster nodes

nshots > taken on those. Please note that host’s FQDNs have been removed. > > > > -Original Message- > From: Bryan Bende > Sent: Wednesday, October 24, 2018 9:25 AM > To: users@nifi.apache.org > Subject: Re: NiFi fails on cluster nodes > > > > Many servic

Re: NiFi Toolkit CLI issues with NiFi/Registry SSL handshake

With the CLI using the keystore/truststore from NiFi you shouldn't get an SSL handshake error at all, regardless of whether it was a command against NiFi or NIFi Registry. After the SSL handshake the command could still fail based on whether the identity of the CLI has permissions to execute the

Re: NiFi fails on cluster nodes

e nifi-user.log also contains > > > > 2018-10-23 12:17:01,916 WARN [NiFi Web Server-224] > o.a.n.w.s.NiFiAuthenticationFilter Rejecting access to web api: Untrusted > proxy CN=, OU=Devices, OU=NIH, OU=HHS, O=U.S. Government, > C=US > > > > From your experience, what

Re: NiFi fails on cluster nodes

00 for client /:50412 > > > > I apologize for bugging you with all this, converting our standalone NiFi > instances into cluster nodes turned out to be much more challenging than we > had anticipated… > > > > -Original Message- > From: Bryan Bende > Sent: Tuesd

Re: NiFi fails on cluster nodes

-cluster-setup On Tue, Oct 23, 2018 at 2:43 PM Bryan Bende wrote: > > So you can get into each node's UI and they each show 1/1 for cluster nodes? > > It doesn't really make sense how the second node would form its own cluster. > On Tue, Oct 23, 2018 at 2:20 PM Saip, Alexander (N

Re: NiFi fails on cluster nodes

xactly the case. > > -Original Message----- > From: Bryan Bende > Sent: Tuesday, October 23, 2018 2:44 PM > To: users@nifi.apache.org > Subject: Re: NiFi fails on cluster nodes > > So you can get into each node's UI and they each show 1/1 for cluster nodes? > > It does

Re: NiFi Toolkit CLI issues with NiFi/Registry SSL handshake

In order to perform any action against a secure registry or NiFi you will need to authenticate, just like if you went to one of the UI's in your browser and you provided a client cert in your browser, or logged in with LDAP/Kerberos/etc. By specifying a truststore you are only verifying the

Re: NiFi fails on cluster nodes

tor Received Connection Request from > :8008; responding with DataFlow that was elected > > 2018-10-24 13:34:12,175 INFO [Process Cluster Protocol Request-2] > o.a.n.c.c.node.NodeClusterCoordinator Status of NodeConnectionStatus[nodeId=:8008, state=CONNECTING, updateId=61] to > No

Re: NiFi Toolkit CLI issues with NiFi/Registry SSL handshake

Can you try editing cli.sh and near the end where it actually executes the CLIMain, edit the line to add the -D for SSL handshake debugging so it looks like this: exec "${JAVA}" -cp "${CLASSPATH}" ${JAVA_OPTS:--Xms128m -Xmx256m} -Djavax.net.debug=ssl:handshake org.apache.nifi.toolkit.cli.CLIMain

Re: NiFi Toolkit CLI issues with NiFi/Registry SSL handshake

-registry-bootstrap.log On Wed, Oct 24, 2018 at 5:24 PM Bryan Bende wrote: > > Can you try editing cli.sh and near the end where it actually executes > the CLIMain, edit the line to add the -D for SSL handshake debugging > so it looks like this: > > exec "${JAVA}" -c

Re: Expression Language

You haven't said which processor/service you are using, but you may want to check the docs for that component to see whether it supports expression language from flow file attributes, some only support variable registry. Most of the elastic search processors look like the host only supports

Re: NiFi Toolkit CLI issues with NiFi/Registry SSL handshake

Glad you were able to get it working. Regarding the super user comment... I don't think it has to be a super user, but it has to be a user that has permissions to perform the action. For your example of "nifi pg-import" it would have to be a user that has write permission to the parent process

<    1   2   3   4   5   6   7   8   >