Re: [DISCUSS] Removal of MissingComponentsCheck from Flow Synchronization

+1 from me, this sounds like the right direction. Virus-free.www.avast.com <#D

Re: [VOTE] Release Apache NiFi 1.18.0 (RC4)

+1 (non-binding) Ran through the build steps, and tested all the new parameter providers, including some scenarios involving adding, removing, and updating parameters from the external source, as well as several referencing component scenarios. Verified that ancestor variable updates do not affec

Re: [VOTE] Release Apache NiFi 1.18.0 (RC3)

+1 (non-binding) Ran through the build steps, and tested all the new parameter providers, including some scenarios involving adding, removing, and updating parameters from the external source, as well as several referencing component scenarios. Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59

Re: New NiFi PMC Member Nathan Gough

Congratulations, Nathan! On Wed, Sep 7, 2022 at 12:12 PM Joe Witt wrote: > Congrats Nathan! > > On Wed, Sep 7, 2022 at 9:10 AM David Handermann > wrote: > > > > Apache NiFi Community, > > > > On behalf of the Apache NiFi Project Management Committee, I am very > > pleased to announce that Natha

Re: [VOTE] Release Apache NiFi 1.17.0 (RC2)

+1 (non-binding) - Ran build and contrib check on Linux with Java 8 - Tested several recent bugs to confirm fixes - Tested interaction with nifi registry Joe On Sat, Jul 30, 2022 at 1:53 PM Joey Frazee wrote: > +1 (binding) > > - Verified signatures and checksums > - Ran full build and contrib

Re: [VOTE] Release Apache NiFi 1.16.0 (rc3)

+1 non-binding - Verified signatures and hashes - Built on Java 8, Mac OS 12 - Tested upgrading a 3-node NiFi 1.15.0 cluster to the release candidate - Verified load balancing on a queue, as well as several recent bugs Joe Gresock On Wed, Mar 23, 2022 at 9:57 AM gre...@yahoo.com.INVALID wrote

Re: [ANNOUNCE] New Apache NiFi Committer Paul Grey

Congrats, Paul! On Wed, Mar 16, 2022 at 9:13 PM Kevin Doran wrote: > Congrats Paul! We’ll deserved > > From: Nathan Gough > Sent: Wednesday, March 16, 2022 9:12:21 PM > To: dev@nifi.apache.org > Subject: Re: [ANNOUNCE] New Apache NiFi Committer Paul Grey > > Co

Re: [VOTE] Release Apache NiFi 1.15.3 (rc1)

+1 (non-binding) Verified signatures and hashes, built from source (MacOS 11.6, Azul Zulu 1.8.0_292), ran a 3-node cluster and some basic flows. On Mon, Jan 17, 2022 at 6:20 PM gre...@yahoo.com.INVALID wrote: > +1 (non-binding) > > - verified signature and hashes of nifi-1.15.3-source-release >

Re: [VOTE] Release Apache NiFi 1.15.1 (rc1)

+1 (non-binding) -- ran through the release guide and ran a basic flow with no problems On Tue, Dec 14, 2021 at 10:35 PM Joe Witt wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache > NiFi 1.15.1. > > This vote, unlike most, is purely stability and security

Re: [VOTE] Release Apache NiFi 1.15.0

+1 (non-binding) Ran through the release helper, tested a clustered flow, stood up nifi-registry and added a registry client to NiFi, version-controlled a processor group, verified several of the recent changes from JIRA. Also ran a few Stateless flows. On Tue, Nov 2, 2021 at 8:52 AM Otto Fowler

Re: [VOTE] Release Apache NiFi 1.15.0 (rc1)

+1 (non-binding) Ran through the release helper, tested a clustered flow, stood up nifi-registry and added a registry client to NiFi, version-controlled a processor group, verified several of the recent changes from JIRA. Tested upgrading a previous version of NiFi, all went well. Joe Gresock

Re: [ANNOUNCE] New NiFi PMC Member David Handermann

Congrats, David! On Fri, Sep 17, 2021 at 9:57 AM Marton Szasz wrote: > Congratulations David! > > On Fri, 17 Sept 2021 at 13:07, Chris Sampson > wrote: > > > > Congrats David, very well deserved! > > > > > > On Fri, 17 Sept 2021 at 13:56, Bryan Bende wrote: > > > > > NiFi Community, > > > > >

Re: Can't connect to Redis Sentinels after upgrading to v.1.14.0

t; session due to All sentinels down, cannot determine where is clnifi > master > >> is running...; Processor Administratively Yielded for 1 sec: > >> redis.clients.jedis.exceptions.JedisConnectionException: All sentinels > >> down, cannot determine where is clnifi

Re: Can't connect to Redis Sentinels after upgrading to v.1.14.0

Thanks for the attached flow, Jens. So just to confirm, if you use Database Index 0, it works on both 1.13.2 and 1.14.0, but if you switch Database Index to 3, it only works on 1.13.2? I was not able to reproduce this in Standalone mode, but I have not tried Sentinel mode. Can you verify whether

Re: [DISCUSS] NiFi 2.0 Release Goals

This sounds like a great path for the 2.0 release. I support goals listed in the NiFi 2.0 Proposed Release Goals page and look forward to the cleanup! Virus-free. www.avas

Re: nifi 1.14.0

Hi Chris, Yes, you can use: ./bin/nifi.sh set-single-user-credentials Joe Virus-free. www.avast.com

Re: [VOTE] Release Apache NiFi 1.14.0 (rc2)

+1 (non-binding) Verified signature and hashes Full build with contrib check with OpenJDK Runtime Environment (Zulu 8.54.0.21-CA-macosx) (build 1.8.0_292-b10) Upgraded a single secure nifi 1.13.2 cluster with an existing flow, which started successfully. Verified TLS 1.3 works using an existing fl

Re: Bug: Load balancer port binds to localhost in cluster, makes load balancer not accessible

Great catch, Jens. I see the mismatch in the properties vs. the code. I just submitted a PR to address this: https://github.com/apache/nifi/pull/5146 On Fri, Jun 11, 2021 at 12:56 AM Jens M. Kofoed wrote: > Dear devoloper > > Please take a look at this jira: > https://lists.apache.org/list.htm

Re: 1.11.3 trust store error

> > in your nifi.properties? Did you have to add the property and give it > the > > > correct value? Or was it in the nifi.properties file but blank? Or > were the > > > keyPasswd and keystorePasswd different values? > > > Thanks, > > > Nathan > > > On Tue

Re: 1.11.3 trust store error

t; >> 4. This exception is coming from inter-node communication > >> (replication > >> > of request from one node to the other). This means that it is > unrelated > >> to > >> > external user's authentication by client certificate. The

Re: 1.11.3 trust store error

E 3C6E F65B 2F7D EF69 > > > On Feb 26, 2020, at 11:07 AM, Joe Gresock wrote: > > > > Ok, I added all the server certs and my administrator's client cert to > the > > trust store, and they all still got PKIX path building failed. So I > > redeployed nifi

Re: 1.11.3 trust store error

Ok, I added all the server certs and my administrator's client cert to the trust store, and they all still got PKIX path building failed. So I redeployed nifi 1.11.1, and now it works again. Joe On Wed, Feb 26, 2020 at 6:21 PM Joe Gresock wrote: > Yes, on Kubernetes. > >

Re: 1.11.3 trust store error

ts to my trust store to see if that works (instead of just adding the client certs' issuer). On Wed, Feb 26, 2020 at 6:08 PM Joe Witt wrote: > on kubernetes is a key detail here too... > > On Wed, Feb 26, 2020 at 10:01 AM Joe Gresock wrote: > > > Java 8 > > > >

Re: 1.11.3 trust store error

Java 8 On Wed, Feb 26, 2020 at 5:59 PM Nathan Gough wrote: > Hi Joe, > > I just set up a secure cluster with NiFi 1.11.3 and am not seeing any > issues like you describe. > > Are you running Java 8 or Java 11? > > Nathan > > On Wed, Feb 26, 2020 at 12:22 PM Joe Gr

1.11.3 trust store error

Were there any changes with how the trust store is used in 1.11.3? I had a 1.11.0 deployment working with the following settings, but when I deployed 1.11.3, the cluster can't seem to replicate requests to itself: nifi.remote.input.host= nifi.remote.input.secure=true nifi.remote.input.socket.port

Re: [jira] [Work logged] (NIFI-6403) ElasticSearch field selection broken in Elastic 7.0+

Is anyone able to test out this patch? I've been using it internally for a few weeks in a patched 1.11.0 cluster, and it works pretty well against both an Elasticsearch 6.3 and an Elasticsearch 7.5 cluster. On Sun, Feb 9, 2020 at 8:50 AM ASF GitHub Bot (Jira) wrote: > > [ > https://issues.

Re: NiFi 1.11.1: EOFException in FlowFileAccessInputStream

org.apache.nifi.controller.repository.io.FlowFileAccessInputStream.read(FlowFileAccessInputStream.java:82) ... 22 common frames omitted On Fri, Feb 14, 2020 at 2:14 PM Joe Gresock wrote: > Good idea. I've made the change, and will report back if I see any more > issues. > > On Fri, Feb 14, 2020 at 2:04 PM Joe Witt wrote: > >>

Re: NiFi 1.11.1: EOFException in FlowFileAccessInputStream

Good idea. I've made the change, and will report back if I see any more issues. On Fri, Feb 14, 2020 at 2:04 PM Joe Witt wrote: > No it should not. But if you want to rule out underlying storage not > getting the writes actually written you can use > > nifi.flowfile.repository.always.sync=true

Re: NiFi 1.11.1: EOFException in FlowFileAccessInputStream

hould NiFi be at risk of truncating content claims in case of the JVM suddenly stopping? On Thu, Feb 13, 2020 at 9:18 AM Joe Gresock wrote: > Sure, sorry for the delay. > > It's an AWS EBS persistent volume. Here are the PV and storage class > objects. It's single-zone (

Re: NiFi 1.11.1: EOFException in FlowFileAccessInputStream

joe.w...@gmail.com wrote: > > > ...sent a little too quick. Also seems like if it is related to your > k8s > > > process that the issue would occur on older nifi releases too. So that > > > might be an interesting test for you. > > > On Mon, Feb 10, 2020 at 9:52 AM Joe Witt j

NiFi 1.11.1: EOFException in FlowFileAccessInputStream

i.stream.io.ByteCountingInputStream.read(ByteCountingInputStream.java:52) at java.io.FilterInputStream.read(FilterInputStream.java:133) at org.apache.nifi.controller.repository.io.FlowFileAccessInputStream.read(FlowFileAccessInputStream.java:82) ... 20 common frames omitted Joe Gresock

zookeeper.admin.enableServer question

I'm checking out the 1.11.0 RC and noticed that in the packaged bootstrap.conf, the following property is set: java.arg.17.=-Dzookeeper.admin.enableServer=false I think this is a typo, as the dot following "17" should not be there, but I didn't want to hold up the RC if this didn't actually have

Elasticsearch 7 patch

Just checking in to see if anyone can look at this patch: https://github.com/apache/nifi/pull/3992 It should provide a way forward with accounting for Elasticsearch breaking changes in the *ElasticsearchHttp processors.

Re: Nifi : FetchS3 object

I've submitted a ticket [1] with a patch included. Sorry it's only 3 years late :) [1] https://issues.apache.org/jira/browse/NIFI-6468 On Wed, Sep 14, 2016 at 5:12 PM James Wing wrote: > I do not believe FetchS3Object currently supports requester-pays buckets. > According to the documentation,

Re: Recovering corrupt flowfile repo

Wed, Nov 21, 2018 at 12:26 AM Joe Gresock wrote: > Ok, I finally found the jar and got it working using java -cp instead of > java -jar. However, I suspect this procedure might not meet my particular > case, because it's looking for parition-* directories, and I don't h

Re: Recovering corrupt flowfile repo

er.ConnectionException: Failed to connect node to cluster due to: java.io.IOException: Expected to read a Sentinel Byte of '1' but got a value of '64' instead Thanks, Joe On Tue, Nov 20, 2018 at 8:18 PM Joe Gresock wrote: > Hi, > > I'm trying to

Recovering corrupt flowfile repo

Hi, I'm trying to restore a corrupt flowfile repo using these instructions: https://community.hortonworks.com/content/supportkb/149943/errorjavaioioexception-expected-to-read-a-sentinel.html I get basically the same error noted on that post. However, the instructions reference a jar called nifi

XKCD use case for NiFi

https://xkcd.com/2054/ He needs NiFi!

Re: Getting more than 500 state values

m_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Nov 22, 2017 at 11:14 AM, Joe Gresock wrote: > I have an UpdateAttribute processor with advanced rules that will store a > coun

Getting more than 500 state values

I have an UpdateAttribute processor with advanced rules that will store a counter for each of 239 attributes in the local state. This appears to work just fine, as I see 956 total state items in the View State view (I have 4 nodes in my cluster). However, I can't seem to retrieve more than 500 it

Re: Long recovery time

elling NiFi to checkpoint the flowfile repository > once an hour instead of the default once every 2 > minutes (via the 'nifi.flowfile.repository.checkpoint.interval' property) > so that would allow us to know what is taking so > long and address accordingly. > > > Thanks

Long recovery time

I have a a NiFi 1.1.0 instance whose disk nearly (but not quite) filled up. I noticed that some of its NiFi processors were hanging so I restarted it, but it's taking over an hour to come back up. My question is: how can I tell if NiFi is doing something productive (and therefore I should just le

Re: QueryRecord error

result. Joe On Mon, Oct 2, 2017 at 4:44 PM, Joe Gresock wrote: > Good question -- no, this must be an artifact of running InferAvroSchema > before the QueryRecord processor. InferAvroSchema infers the schema and > places it in a flow file attribute, which the CSVReader us

Re: QueryRecord error

am?) Is it > possible that you just selected > the wrong reader? > > Thanks > -Mark > > > On Oct 2, 2017, at 12:24 PM, Joe Gresock wrote: > > > > I'm changing the subject name so as not to muddy the [VOTE] thread. > > > > I finally found the error i

QueryRecord error

ort of failure -- typically, a failure to obtain > the schema for the Record Reader > or Record Writer. Can you check your logs for any other errors that may be > occurring? > > Thanks > -Mark > > > > On Oct 2, 2017, at 11:32 AM, Joe Gresock wrote: > > > > I

Re: [VOTE] Release Apache NiFi 1.4.0 (RC2)

I have to change my non-binding +1 vote to a 0, unless there is a workaround for the bug [1] I just submitted, regarding the QueryRecord processor being broken. [1] https://issues.apache.org/jira/browse/NIFI-4452 On Mon, Oct 2, 2017 at 3:23 AM, Kevin Doran wrote: > +1, non-binding > > - Verif

Re: [VOTE] Release Apache NiFi 1.4.0 (RC2)

+1 (non-binding) Built on CentOS 7, upgraded an existing 1.3.0 cluster, ran a complex flow with self-RPGs, reporting tasks, and controller services. All looks good! The Avro viewer is especially nice, and the double-click feature already feels natural. Great work! On Sun, Oct 1, 2017 at 4:41 PM

Re: Url encoding with S3 processors

f we decoded by default, we > could create confusion with unexpected key changes. > > Thanks, > > James > > On Thu, Sep 7, 2017 at 6:59 AM, Joe Gresock wrote: > > > Has anyone run into any URL encoding issues with the AWS nifi processors > in > > version 1.

Url encoding with S3 processors

Has anyone run into any URL encoding issues with the AWS nifi processors in version 1.3.0? My flow has GetSQS and then FetchS3Object, along with the AWS feature of automated SQS events upon S3 file upload. Some of my S3 objects apparently have characters in their object keys that need to be URL e

Re: Recovery failure

ld be contributed, or is it moot with the latest version? Joe On Wed, Sep 6, 2017 at 5:18 PM, Joe Gresock wrote: > Thanks Mark, that's the kind of thing I was looking for, this gives me a > good starting point. > > Joe > > On Wed, Sep 6, 2017 at 5:09 PM, Mark Payne w

Re: Recovery failure

gt; nextPartition.getNextRecoverableTransactionId() again > if the partition does actually have more data (may require > adding some sort of isRecoveryDataAvailable() method or something > like that on the Partition class). > > Does this help? > > Thanks > -Mark > > &g

Re: Recovery failure

MinimalLockingWriteAheadLog could be updated to not assume that EOFException > implies that the partition no longer has data in it. Unfortunately, > though, I'm not seeing any easy work around. > > > On Sep 6, 2017, at 12:37 PM, Joe Gresock wrote

Re: Recovery failure

/flowfile_ > repository/partition-8, > how many files are there in there, and how large are they? > > Thanks > -Mark > > > > On Sep 6, 2017, at 12:22 PM, Joe Gresock mailto:jgr > es...@gmail.com>> wrote: > > 1.1.0, it's not on a system I can copy/p

Re: Recovery failure

iFI are you running? Do you have a stack trace? > > Thanks > -Mark > > > > On Sep 6, 2017, at 11:59 AM, Joe Gresock wrote: > > > > I'm wondering if there is a way to recover from this scenario: > > > > ERROR [main] o.a.nifi.contr

Recovery failure

I'm wondering if there is a way to recover from this scenario: ERROR [main] o.a.nifi.controller.StandardFlowService Failed to load flow from cluster due to: org.apache.nifi.cluster.ConnectionException: Failed to connect node to cluster due to: java.lang.IllegalStateException: Signaled end to recov

Re: No enum constant org.wali.UpdateType.CONTENTMISSING

ce=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On

No enum constant org.wali.UpdateType.CONTENTMISSING

I'm trying to recover from a crash where some data was lost from the content_repository. Any advice on getting past this particular error? I checked and sure enough, there's no enum constant called UpdateType.CONTENTMISSING in the NiFi 1.3.0 code (not sure how that value got in there in the first

Re: NiFi 1.3.0 Remote ports "disabled" after a while?

://issues.apache.org/jira/browse/NIFI-4075 > > -Bryan > > On Thu, Jun 15, 2017 at 10:14 AM, Joe Gresock wrote: > > Btw, I was wrong about one statement in my last email.. this particular > RPG > > (705cd4bd-1b98-3c4b-b467-c455ad52fd90) IS in the state where some nodes &g

Re: NiFi 1.3.0 Remote ports "disabled" after a while?

, 2017 at 2:07 PM, Joe Gresock wrote: > Great questions, Koji: > > 1. RAW > 2. Push > 3. No, compression is not enabled > 4. Several, but it has the same effect to "Enable transmission" as it does > to specifically disable and then enable a specific port. The key being

NiFi 1.3.0 Remote ports "disabled" after a while?

Before I investigate further, has anyone encountered NiFi RPGs "disabling" after a while in 1.3.0? Their status is reported as enabled/transmitting, but the flow files just sit there until I "enable transmission" again. This happens for nearly all of the RPGs I have in my flow. I just have to kee

Re: How to update attribute based on text file contents?

It sounds like Dave is trying to use the content of a text file on the file system, not from a flow file. Dave, can you describe the use case in more detail? There are a couple processors that use files from the file system (e.g., ReplaceTextWithMapping), but I can't tell if it would fit in your

Re: NIFI-4104

lude in there. > > Thanks > > Matt > > On Mon, Jun 5, 2017 at 12:16 PM, Joe Gresock wrote: > > > I just built the master codebase last week and found a typo on the S2S > > provenance reporting task and thought it would be nice to fix it ([1]) > for > >

NIFI-4104

I just built the master codebase last week and found a typo on the S2S provenance reporting task and thought it would be nice to fix it ([1]) for the 1.3.0 release. This is a one-liner.. anyone care to review it? [1] https://issues.apache.org/jira/browse/NIFI-4014 -- I know what it is to be in

Re: Release Management for Apache NiFi 1.3.0 and 0.7.4

Just wanted to put in a request for anyone to look at [1] before the 1.3.0 release, if possible. It's a tough one because it's hard to reproduce, but I feel like its cause could be deduced by inspecting any changes in the flowfile/content repositories between version 1.1.1 and 1.2.0 (since the pro

Re: Contributing templates

Thanks Joe! I've added the template. On Tue, May 23, 2017 at 2:17 AM, Joe Witt wrote: > Both Pierre and Joe can contribute on the wiki now. > > Thanks! > > On Mon, May 22, 2017 at 9:26 PM, Joe Gresock wrote: > > Thanks Pierre! > > > > So, now that you ar

Re: Contributing templates

onfluence/display/NIFI/ > Example+Dataflow+Templates > > Pierre > > 2017-05-20 16:55 GMT+02:00 Joe Gresock : > > > All, > > > > Is there a place to contribute templates? I have a template for using > the > > SiteToSiteStatusReportingTask along with Conver

Contributing templates

All, Is there a place to contribute templates? I have a template for using the SiteToSiteStatusReportingTask along with ConvertRecord and PutElasticsearchHttp that automatically stores NiFi's status history in an Elasticsearch database for long term analysis of NiFi status history. If there is a

Re: NiFi 1.2.0 Record processors question

ing is still helpful in those cases too. > > Hopefully I am making sense and not confusing things more. > > > On Fri, May 19, 2017 at 1:27 PM, Joe Gresock wrote: > > Matt, > > > > Great response, this does help explain a lot. Reading through your post > &

Re: NiFi 1.2.0 Record processors question

is would require two reads, one by > AddSchemaAsAttribute and one by the downstream record processor, but > it should be fairly easy to implement. Then again, since new features > would go into 1.3.0, hopefully NIFI-3921 will be implemented by then, > rendering all this moot :) > >

NiFi 1.2.0 Record processors question

I've tried a couple different configurations of CSVReader / JsonRecordSetWriter with the QueryRecord processor, and I don't think I quite have the usage down yet. Can someone give a basic example configuration in the following 2 scenarios? I followed most of Matt Burgess's response to the post ti

Re: All processors stopped on startup

a single node.) This happened several times, but on at least > one occasion they remained running. I am pretty sure that in my case when > the UI showed them stopped they really were stopped, and not running > surreptitiously. > > On Fri, May 12, 2017 at 12:10 PM, Joe Gresock wr

Re: All processors stopped on startup

UI, which prevents me from starting any processors that happen to have a thread running. On Fri, May 12, 2017 at 4:08 PM, Joe Gresock wrote: > I upgraded a nifi 1.1.1 cluster to 1.2.0, and I'm now finding that all > processors are stopped on startup. However, the flow.xml.gz on disk &

All processors stopped on startup

I upgraded a nifi 1.1.1 cluster to 1.2.0, and I'm now finding that all processors are stopped on startup. However, the flow.xml.gz on disk appears to have the correct scheduledState values. I'm afraid to touch the flow in the UI, lest it save all 500 of my processors as stopped. Is there anythin

Re: 1.2.0 upgrade label colors lost?

[2], I've reopened the issue to investigate the > underlying issue. > > Matt > > [1] https://issues.apache.org/jira/browse/NIFI-3829 > [2] > https://nifi.apache.org/docs/nifi-docs/html/user-guide. > html#browser-support > > On Thu, May 11, 2017 at 1:06 PM, Joe Gres

NIFI-2199 back? nifi.sh start hanging again in 1.2.0

After upgrading our cluster to 1.2.0, the problem described in [1] appears to be back. On a 1.1.1 cluster, I can issue the following command, which exits ssh appropriately with a return code of 0: ssh stage-nifi1 "sudo service nifi start" On 1.2.0, the same command correctly starts nifi, but the

Re: 1.2.0 upgrade label colors lost?

nks > > Matt > > On Thu, May 11, 2017 at 12:37 PM, Joe Gresock wrote: > > > I just upgraded an existing NiFi 1.1.1 cluster to 1.2.0 and the label > > colors appear to be gone. I can see them in the Navigate view, but in > the > > main view the labels are just cle

1.2.0 upgrade label colors lost?

I just upgraded an existing NiFi 1.1.1 cluster to 1.2.0 and the label colors appear to be gone. I can see them in the Navigate view, but in the main view the labels are just clear. This also affects new labels that I add. I cleared my browser cache and reloaded with the same results. Has anyone

Re: Closing in on a NiFi 1.2.0 release?

Would it be appropriate to add mention of the 2 new site-to-site reporting tasks (status and bulletin) in the release notes? Virus-free. www.avast.com

Re: Hostname does not match

Just to follow up -- apparently if the Subject Alternate Name is set incorrectly, it will result in this error. Apparently the CN is ignored if the SAN is set on the cert. On Sat, Apr 22, 2017 at 12:08 PM, Joe Gresock wrote: > I've been banging my head against the wall on this one.. is

Hostname does not match

I've been banging my head against the wall on this one.. is there a good way to further debug this RPG error? The hostname clearly matches the certificate CN. 2017-04-22 12:04:35,932 WARN [Remote Process Group 68ed2275-894d-3d75-b457-9d28a1b680e0: https://ip-172-31-33-37.ec2.internal:8443/nifi Th

Re: AWS processor credentials question

> configuration required, just the controller service. Is that not working? > Which version of NiFi do you have? > > On Thu, Apr 13, 2017 at 9:04 AM, Joe Gresock wrote: > > > My thought was to make the default value be set to "True" (to allow > > anonymou

Re: AWS processor credentials question

possibly incompatible with a minor > release. > > Thanks, > > James > > On Thu, Apr 13, 2017 at 6:40 AM, Joe Gresock wrote: > > > Ok, I submitted a PR [1] for this ticket. The change is only additive > and > > should be non-invasive to existing processors.

Re: AWS processor credentials question

Ok, I submitted a PR [1] for this ticket. The change is only additive and should be non-invasive to existing processors. If one of you could review it, it might even be nice to get into the 1.2.0 build. [1] https://github.com/apache/nifi/pull/1671 On Thu, Apr 13, 2017 at 10:33 AM, Joe Gresock

Re: AWS processor credentials question

Actually it's a little more complicated than the code I suggested, since DefaultAWSCredentialsProviderChain.getInstance() is an AWSCredentialsProvider, not an AWSCredentials object. But the idea would be similar. On Thu, Apr 13, 2017 at 10:21 AM, Joe Gresock wrote: > AWS-related d

AWS processor credentials question

AWS-related devs (I'm looking at James Wing and Adam Lamar), I just added [1] to propose allowing AWS processors to specify whether to use anonymous credentials or to use the default AWS client credentials provider chain. The driver for this is that we would like to use EC2 instance profiles with

Re: Reporting task for capturing status history?

74 On Wed, Apr 5, 2017 at 3:52 PM, Joe Gresock wrote: > Thanks Mark! I've created [1] to capture this request. I started writing > a SiteToSiteStatusReportingTask by modifying a copy of the > SiteToSiteProvenanceReportingTask, but I got diverted with other tasks > and probably wo

Re: UI Javascript error in master?

Sorry.. that was supposed to be nifi-canvas-utils.js:415 On Fri, Apr 7, 2017 at 1:54 PM, Joe Gresock wrote: > Some more info, since that stack trace wasn't really helpful: the error is > reported at nf-canvas-all.js, line 15, char 4127, which is this section: > > var x=new UR

Re: UI Javascript error in master?

r paramsObject = {}; *415params.forEach(function (v, k) {* 416paramsObject[k] = v; 417}); P.S., just saw Matt's response. It was a fresh install, empty flow. My url string was: http://localhost:8080/nifi/ Firefox is version 45.8.0 on CentOS

UI Javascript error in master?

I pulled down, built, and deployed the master branch this morning, and I'm getting the following error in Firefox when I try to pull up the console. The console doesn't get past the loading screen, though I'm not sure if this error is related: TypeError: x.forEach is not a function f.setURLParame

Re: Reporting task for capturing status history?

ansfer attributes > along with the 'message' if it makes sense to do so, and integrates very > cleanly. You could then use > whatever Processors make sense in your flow to push the data wherever you > would like it to be. > > Thanks > -Mark > > > > > On

Reporting task for capturing status history?

I haven't completely kept up to date on the new reporting tasks since 1.1.1, so I thought I'd ask here. I'd like to be able to store the status history metrics for processors and queues in something like Elasticsearch. I see the StandardGangliaReporter, which looks to capture what I want, but I'm

Re: DistributedMapCacheServer question

t; > On Mar 9, 2017, at 10:24 AM, Joe Gresock wrote: > > > > Good instinct -- here's what I get: > > > > nifi-app.log:2017-03-09 15:03:00,670 INFO [Distributed Cache Server > > Communications Thread: ac907dec-49a4-439e-99f5-1558f2358d87] > > org.wali.M

Re: DistributedMapCacheServer question

e FlowFile Repository, > one for Local State Management, and another one for the > DistributedMapCacheServer. I am curious to see if > you see the log message indicating 3 million+ records also. > > Thanks > -Mark > > > > On Mar 8, 2017, at 7:13 PM, Joe Gresock wro

Re: DistributedMapCacheServer question

8, 2017 at 11:06 AM, Joe Gresock wrote: > Thanks Bryan, I'll start looking through the PersistenceMapCache. This > morning I checked back and the snapshot file now has 2.9 million keys in it. > > On Tue, Mar 7, 2017 at 4:39 PM, Bryan Bende wrote: > >> Joe, >> &g

Re: DistributedMapCacheServer question

check point every > 100k and and deletes check point every 1k. > > Maybe Mark or others could shed some light on why the snapshot is > reaching 3GB in size. > > -Bryan > > > On Tue, Mar 7, 2017 at 7:07 AM, Joe Gresock wrote: > > Hi folks, > > > > Is the

DistributedMapCacheServer question

Hi folks, Is there a technical description of how the DistributedMapCacheServer (DMCS) persistence works? I've noticed the following on our cluster: - I have the DMCS configured on port 4557 as FIFO with max 100,000 entries, and have specified a persistence directory - I am using DetectDuplicate

Re: Closing in on a NiFi 1.2.0 release?

This is good discussion that should continue, but what about the original intent of Joe's post? "Is there any reason folks can think of to hold off on a 1.2.0 release?" On Fri, Mar 3, 2017 at 1:45 PM, Mark Payne wrote: > Andy, > > Sorry, i haven't responded to this thread in over a week, but I

Re: Hosting API's on Nifi

I believe the traditional approach would be to specify another port like 8443 in the NiFi HandleHttpRequest processor, and use a reverse proxy like nginx or httpd running on 80/443 that directs traffic to NiFi. We have done this on our own project, and there are several articles floating around on

Re: Closing in on a NiFi 1.2.0 release?

Slightly off topic, but your statement "we need reviews/feedback as much as we need contributions" made me think that the project could somehow benefit from the concept of Kanban Work In Progress limits. Not sure how you'd implement this with an open source project, but just a thought. On Thu, Fe

Re: Nifi in a hung state

Sam, if I remember correctly, you will have to list the entire bucket (optionally with the matching prefix) once in order to store the last-seen object key/version and its timestamp in the NiFi processor state. After you do this initial listing, ListS3 will then behave as you describe, where it wi

  1   2   >