Re: Closing in on a NiFi 1.2.0 release?

All, For some reason my canvas did not refresh after a process bounce (which generally occurs) but reloading page allows for modifications. Cheers On Wed, May 3, 2017 at 7:43 AM, Andre wrote: > folks, > > I was just working to debug the final thorns found reviewing

Re: Closing in on a NiFi 1.2.0 release?

folks, I was just working to debug the final thorns found reviewing NIFI-3726 and noticed an odd behavior and wanted to confirm. If I recall correctly in the past users could simply replace a processor NAR file and even if that NAR existed the flow would continue to work. I just replaced cp

Re: failed to replicate request GET /NIFI-API/flow/process-groups/root to saxx:9090

thanks Matt, will do and let you know soon. -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/failed-to-replicate-request-GET-NIFI-API-flow-process-groups-root-to-saxx-9090-tp15612p15626.html Sent from the Apache NiFi Developer List mailing list archive at

Re: failed to replicate request GET /NIFI-API/flow/process-groups/root to saxx:9090

thanks Bryan, I could not open the console on http://sabc.abcd.local:9090/nifi. -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/failed-to-replicate-request-GET-NIFI-API-flow-process-groups-root-to-saxx-9090-tp15612p15625.html Sent from the Apache NiFi

Re: Closing in on a NiFi 1.2.0 release?

I’ll review & merge as soon as they are available. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On May 2, 2017, at 3:51 PM, Bryan Bende wrote: > > Thanks Drew. These seem like good

Re: Closing in on a NiFi 1.2.0 release?

Thanks Drew. These seem like good candidates for the release. On Tue, May 2, 2017 at 3:42 PM, Andrew Lim wrote: > There are three doc updates/additions that would be great to include in the > RC: > > https://issues.apache.org/jira/browse/NIFI-3701 >

Re: Closing in on a NiFi 1.2.0 release?

There are three doc updates/additions that would be great to include in the RC: https://issues.apache.org/jira/browse/NIFI-3701 https://issues.apache.org/jira/browse/NIFI-3773 https://issues.apache.org/jira/browse/NIFI-3774 Sarah Olson and I have been working on these. We should have PRs

Re: how to write date to redis

Jython is not the most performant script engine, if you are familiar with Groovy or Javascript I would recommend porting to one of those for better performance. There are some examples [1] [2] of in-progress development of Redis processors for NiFi. Although they are fetching from Redis, not

Re: Not able to ingest the csv data to RDBS Database

In order for ReplaceText to reference ${city} and ${count} there need to be flow file attributes available for these values, and if you picked up a file from GetFile and went directly to ReplaceText then they wouldn't be there. You would likely have to do something like GetFile -> SplitText with

Re: failed to replicate request GET /NIFI-API/flow/process-groups/root to saxx:9090

Pradeep, Trying increasing the cluster read timeout. It's specified in property nifi.cluster.node.read.timeout You'll need to update this configuration on each node of your cluster as it's relevant for the node currently acting as the coordinator. Thanks Matt On Tue, May 2, 2017 at 2:37 PM,

Re: failed to replicate request GET /NIFI-API/flow/process-groups/root to saxx:9090

Pradeep, This means the NiFi you are accessing the UI from is trying to replicate a request to another NiFi in the cluster running on sabc.abcd.local:9090 and couldn't complete the replication due to a read timeout. Can you verify there is a NiFi running at sabc.abcd.local:9090? Can you access

Re: how to write date to redis

Hello, I can't say for sure why your script isn't performing well, but I would guess that you would get better performance from a custom processor written in Java that wrapped a Redis client like Jedis. If you are interested in working on this I think it would be something the community would be

Re: nifi-extension-utils

Thanks for doing this, Bryan. As part of the PR for NIFI-1833 (Azure Storage Blob processors), I've moved AbstractListProcessor (and some supporting classes) into nifi-commons/nifi-processor-utils, and had to rebase for this change. It was a pretty simple process. If anyone else needs help

Re: Closing in on a NiFi 1.2.0 release?

Haven't had much luck in getting our Docker efforts incorporated into Docker Hub. As a result I have created an issue to track that integration [1] and resolved the original issue. We can evaluate our options and figure out the best path forward. At this time procedures are not yet well

Re: External ZooKeeper

Mark, I've been using https://zookeeper.apache.org/doc/r3.4.10/ [1] and subscribed to their user alias [2] similar to Apache NIFI, they have been responsive when I've asked them questions. It was easy for me to adapt to using an external zookeeper since configuration wise its pretty much the same

Not able to ingest the csv data to RDBS Database

Hi , I have a csv file and i want to ingest the csv file data into the database. I have used getfile,RelaceText,PutSQL Processors. It's failing in replaceText Processor. File Sample : City,Count Mumbai,10 Mumbai,10 Pune,10 Pune,10 ReplaceText : INSERT INTO CITY(city,count) values

External ZooKeeper

Is there a guide, blog, FAQ or other documentation on setting up a dedicated external ZooKeeper (not the embeddded ZooKeeper) for a NiFi Cluster? Thanks, Mark

failed to replicate request GET /NIFI-API/flow/process-groups/root to saxx:9090

hello folks, I see this exception, and can not open the NIFI console.There is connectivity between the nodes in the cluster on port 9090.Any clues would help. 2017-05-02 11:50:18,607 WARN [Replicate Request Thread-2] o.a.n.c.c.h.r.ThreadPoolRequestReplicator Failed to replicate request GET

Re: Data Load

Yes that sounds like your best bet, assuming you have the "Maximum Value Column" present in the table you want to migrate. Then a flow might look like: QueryDatabaseTable -> ConvertAvroToJSON -> ConvertJSONToSQL -> PutSQL In this flow the target tables would need to be created beforehand. You

Re: Data Load

Thanks Matt for the quick reply. We are using nifi 1.0 release as of now. It's a postgres DB on both sides (on prem and on cloud) and yes incremental load is what i am looking for. so with that, you recommend # 2 option? On Tue, May 2, 2017 at 11:00 AM, Matt Burgess

Re: Closing in on a NiFi 1.2.0 release?

I will be making updates to the Release Notes and Migration Guidance doc regarding the TLS 1.2 version support. Tracked by: https://issues.apache.org/jira/browse/NIFI-3720 -Drew > On May 2, 2017, at 11:08 AM, Joe Witt wrote: > > Those are great updates. I'd recommend

Re: MiNiFi CPP indentation confusion (Re: MINIFI-244)

Sounds good, thanks. From: Marc P. Sent: Tuesday, May 2, 2017 11:12:02 AM To: dev@nifi.apache.org Subject: Re: MiNiFi CPP indentation confusion (Re: MINIFI-244) Andy, That will be solved with MINIFI-226. You will only need to call

Re: MiNiFi CPP indentation confusion (Re: MINIFI-244)

Andy, That will be solved with MINIFI-226. You will only need to call REGISTER_RESOURCE(classname) or REGISTER_RESOURCE_AS(classname,name) in your header file and it will automatically be loadable via the name. You are correct though, we can alias the namespace ( and we do in core/Core.h).

Re: MiNiFi CPP indentation confusion (Re: MINIFI-244)

OK, I can work with that. Does the style guide allow for cleaning up this bit? if (name == org::apache::nifi::minifi::processors::GenerateFlowFile::ProcessorName) { processor = std::make_shared< org::apache::nifi::minifi::processors::GenerateFlowFile>(name, uuid); } else if

Re: Closing in on a NiFi 1.2.0 release?

Those are great updates. I'd recommend we avoid highlighting the versions of UI components though. Thanks On Tue, May 2, 2017 at 11:03 AM, Scott Aslan wrote: > Hey Bryan, > > Please include the following in the release notes: > > >- Core UI > - Circular

Re: Closing in on a NiFi 1.2.0 release?

Quick update... I was looking through PRs and noticed that NIFI-3594 (Encrypted Prov Repo) had already received a +1 and just needed an update to resolve conflicts with master. I spoke to Andy offline and he is planning to resolve the conflicts shortly and we can include this in 1.2.0. Also,

Re: MiNiFi CPP indentation confusion (Re: MINIFI-244)

Hi Andy, I’ll let a minify-cpp veteran jump in if I have this wrong, but I believe we are following the Google C++ Style Guide [1]. As it is my first time following this style, it caused me to do a double take as well :-) The Google C++ Style Guide does specify entries under public, protected,

Data Load

I have a simple use case. DB (On Premise) and DB (On Cloud). I want to use nifi to extract data from on prem DB (huge volumes) and insert into the same table structure that is hosted on cloud. I could use ExecuteSQL on both sides of the fence (to extract from on prem and insert onto cloud).

Re: MiNiFi CPP indentation confusion (Re: MINIFI-244)

On closer inspection, it looks like just the public/private/etc. specifiers are single-space indented, with the rest being two-spaces. Is this intentional? From: Andrew Christianson Sent: Tuesday, May 2, 2017 10:33:27 AM To: dev@nifi.apache.org Subject:

MiNiFi CPP indentation confusion (Re: MINIFI-244)

Working on merging my code for MINIFI-244 with the latest refactoring where all of the classes have been put into nested namespaces. Looking at sibling files, it looks like several of them are indented with one space. This surprises me. What's the preferred indentation/code style? Two spaces?

Re: [CALL FOR ACTION] Peer reviews & testing of new code

Thanks for pointing out that *contributions *of Reviewing code are still valid and that its not a *committer *only job! On Mon, May 1, 2017 at 7:17 PM, Andre wrote: > Dev, > > Those following the git commit log probably noticed that there has been a > lot of action by some

Re: Closing in on a NiFi 1.2.0 release?

All, Looks like we are closer than we have ever been! Down to three outstanding JIRAs... - NIFI-1833 (Azure Processors) - Active review and discussion occurring, appears to be close - NIFI-3260 (Official Docker Image) - Active discussion, looks like this may be moved from the release to a