Re: Review PR 2020 - Add PutKudu Processor for Kudu

t? > > https://github.com/apache/nifi/pull/2020 > > > > Jira: https://issues.apache.org/jira/browse/NIFI-3973 > > > > Thanks, > > Cam Mach > > Inspur USA > -- Ricky Saltzer http://www.cloudera.com

RE: [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Registry

I'm a big +1 to this proposal. It would solve a huge burden that is keeping NARs up to date in environments where there's alot of teams that share NARs but have separate NiFi deployments and repositories. On Feb 8, 2017 7:09 PM, "Peter Wicks (pwicks)" wrote: > I think a lot

Re: Unable to List Queue with Policy

Joe - You're a life saver! Cheers! Ricky On Tue, Dec 6, 2016 at 2:21 PM, Joe Gresock <jgres...@gmail.com> wrote: > Hi Ricky, > > I ran into this recently: you have to give your proxying server access to > View the Data. > > On Tue, Dec 6, 2016 at 7:15 PM, Ricky Sal

Unable to List Queue with Policy

Hi - I am struggling with allowing myself to list any connection queue. I have given myself every permission possible for the entire data flow, but even still, I am told I do not have permission to list a data queue. In addition, there is seemingly zero records in the provenance reporter, even

Re: Secure Cluster Mode Issues

es.apache.org/jira/browse/NIFI- > [2] https://issues.apache.org/jira/browse/NIFI-2466 > > > Andy LoPresto > alopre...@apache.org > *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>* > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > On Nov 30, 20

Re: Secure Cluster Mode Issues

sword into a login field on their > first connection to NiFi and be authenticated. > > > Andy LoPresto > alopre...@apache.org > *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>* > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > On N

Re: Secure Cluster Mode Issues

; --- > > The important part is the last line — you want the *Verify return code* to > be 0 for success. Once you have verified this, run the TLS toolkit again to > generate a valid client certificate: > > $ ./bin/tls-toolkit.sh standalone -C 'CN=Ricky Saltzer, OU=Apache

Re: Secure Cluster Mode Issues

uld create a certificate identifying the server itself, so the CN is > the FQDN as mentioned above. Then import into (or generate directly inside) > the keystore. You can also use the provided NiFi TLS Toolkit to automate > this entire process [2]. > Certificate chain > 0 s:/C=CA/ST=CA

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

> Release+Notes#ReleaseNotes-Version1.1.0 > > > > > > > > The vote will be open for 72 hours. > > > > Please download the release candidate and evaluate the necessary > items > > > > including checking hashes, signatures, build from source, and test. > > Then > > > > please vote: > > > > > > > > [ ] +1 Release this package as nifi-1.1.0 > > > > [ ] +0 no opinion > > > > [ ] -1 Do not release this package because... > > > > > > > > Thanks! > > > > > > > > > > > > > > > -- > > *Scott Aslan = new WebDeveloper(* > > *{"location": {"city": "Saint Cloud","state": "FL", > >"zip": "34771"},"contact": {"mobile": > > "(321)-591-0870","email": "scottyas...@gmail.com > > <scottyas...@gmail.com>","linkedin": > > "http://www.linkedin.com/in/scottaslan > > <http://www.linkedin.com/in/scottaslan>","skype": "astechdev" > > }});* > > > -- Ricky Saltzer http://www.cloudera.com

Re: Secure Cluster Mode Issues

Payne <marka...@hotmail.com> wrote: > Hey Ricky, > > When you enable debug logging for SSL, it writes to StdErr (or StdOut?) so > it will end up in your logs/nifi-bootstrap.log instead of nifi-app.log. > Can you give that a look? > > Thanks > -Mark > > > On

Re: Secure Cluster Mode Issues

F D3C4 BACE 3C6E F65B 2F7D EF69 > > On Nov 2, 2016, at 2:25 PM, Ricky Saltzer <ri...@cloudera.com> wrote: > > Hey all - > > I'm using NiFi 1.0 and I'm having an issue using secure mode with a local > key store while in clustered mode. If I set the node in clustered mode, an

Secure Cluster Mode Issues

Hey all - I'm using NiFi 1.0 and I'm having an issue using secure mode with a local key store while in clustered mode. If I set the node in clustered mode, and also provide a valid keystore, I receive a KeyStoreException [1]. If I set the configuration to not use clustered mode, NiFi will start

Re: Content Repository Cleanup Schedule

urious how many files there are and how many are "large" files. > > > > > On Jun 15, 2016, at 5:02 PM, Ricky Saltzer <ri...@cloudera.com> wrote: > > > > Is it safe to manually remove some of the older files in the repository > to > > avoid ou

Re: Content Repository Cleanup Schedule

Is it safe to manually remove some of the older files in the repository to avoid our disk from filling up? On Wed, Jun 15, 2016 at 4:55 PM, Ricky Saltzer <ri...@cloudera.com> wrote: > Just a reminder, I just today noticed the "archive.enabled" option was > false

Re: Content Repository Cleanup Schedule

s there is anything to > reclaim. > > Can you try going to your content repository and running: > > find . -type f -ls | grep archive > > Curious as to how much data it has archived. > > > On Jun 15, 2016, at 4:48 PM, Ricky Saltzer <ri...@cloudera.com> wrote:

Re: Content Repository Cleanup Schedule

Oh sorry! Trying again [1] https://gist.githubusercontent.com/rickysaltzer/b00196a3881c052df9b38b418722cd02/raw/279a1bc8c60530426732eb7b653de1f3f74574e2/gistfile1.txt On Wed, Jun 15, 2016 at 4:38 PM, Ricky Saltzer <ri...@cloudera.com> wrote: > I should also mention, I just realized

Re: Content Repository Cleanup Schedule

I should also mention, I just realized that our worker nodes are on 0.5.1, and for some reason I missed updating the master from 0.4.0. I'm sure that is not helping. On Wed, Jun 15, 2016 at 4:36 PM, Ricky Saltzer <ri...@cloudera.com> wrote: > Looks like the threads are parked and w

Re: Content Repository Cleanup Schedule

ke a look at mark's note as that is > probably more relevant to your case. > > On Wed, Jun 15, 2016 at 4:32 PM, Ricky Saltzer <ri...@cloudera.com> wrote: > > Hey Joe - > > > > The NiFi web UI currently reads as: > > > > Active threads: 3 > > Queued: 10,173 /

Re: Content Repository Cleanup Schedule

the > flow/queued up? And then if that is the case are we talking about a > roughly 1TB repo and so the reported value seems correct and this is > simply a case of queueing near to the limit your system can hold? > > On Wed, Jun 15, 2016 at 4:24 PM, Ricky Saltzer <ri...@cloudera.com> wrote: > > I ha

Re: Content Repository Cleanup Schedule

ou restart nifi and then find that it cleans those things up I > believe then it is related to the defects corrected in the 0.5/0.6 > timeframe. > > Is restarting an option for you at this time. You agree mark? > > Thanks > Joe > > On Wed, Jun 15, 2016 at 4:21 PM, Ricky Saltze

Re: Content Repository Cleanup Schedule

ed up in your > flow? > Data won't be archived or reclaimed if in the flow. > > Thanks > -Mark > > > > > On Jun 15, 2016, at 4:04 PM, Ricky Saltzer <ri...@cloudera.com> wrote: > > > > Hey guys - > > > > I recently discovered I didn'

Content Repository Cleanup Schedule

Hey guys - I recently discovered I didn't have my "archive.enabled" option set to true after my disk filled up to 95%. I enabled it and then set the retention period to 12 hours and 50% (default values). However, after restarting NiFi, I am not seeing any disk space reclaimed. I'm curious, is

Re: StoreInKiteDataset cant validate URI

.com/StoreInKiteDataset-cant-validate-URI-tp10409.html > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. > -- Ricky Saltzer http://www.cloudera.com

Re: Trouble with the LDAP Authentication Provider

[3] https://gist.github.com/alopresto/e6bca539876fe4324f49e4996f41c91a > [4] https://gist.github.com/alopresto/06938e4d0ccdf2168fe0fc6158780a56 > > Andy LoPresto > alopre...@apache.org > *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>* > PGP Fingerprint: 70EC B3E5 98

Re: Trouble with the LDAP Authentication Provider

get back to you Monday? > > Andy LoPresto > alopre...@apache.org > *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>* > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > On May 13, 2016, at 1:47 PM, Ricky Saltzer <ri...@cloudera.com

Re: Trouble with the LDAP Authentication Provider

Andy LoPresto > alopre...@apache.org > *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>* > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > On May 12, 2016, at 2:26 PM, Ricky Saltzer <ri...@cloudera.com> wrote: > > Using the following provider on

Trouble with the LDAP Authentication Provider

Using the following provider on 0.6.1, I'm faced with a ClassCastException. It might also be worth noting that I face the same exception when attempting to us the KerberosProvider option. *Provider:* ldap-provider org.apache.nifi.ldap.LdapProvider SIMPLE dethklok\toki

Re: parquet format

; -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/parquet-format-tp10145p10186.html > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. > -- Ricky Saltzer http://www.cloudera.com

Re: [ANNOUNCE] New Apache NiFi Committer James Wing

it is greatly appreciated. We look forward to > > his > > > > > continued involvement in the project. > > > > > > > > > > Welcome and congratulations! > > > > > > > > > > > > > > > > > -- > Thanks, > Andrew > > Subscribe to my book: Streaming Data <http://manning.com/psaltis> > <https://www.linkedin.com/pub/andrew-psaltis/1/17b/306> > twiiter: @itmdata <http://twitter.com/intent/user?screen_name=itmdata> > -- Ricky Saltzer http://www.cloudera.com

Re: parquet format

t format ?.Please advice > >> > >> Thanks > >> Pradeep > >> > >> > >> > >> -- > >> View this message in context: > >> > http://apache-nifi-developer-list.39713.n7.nabble.com/parquet-format-tp10145.html > >> Sent from the Apache NiFi Developer List mailing list archive at > >> Nabble.com. > >> > -- Ricky Saltzer http://www.cloudera.com

Re: [discuss] PropertyDescriptor name and displayName attributes

An idea I had is to modify the API and use a setter that would require both the name and the display name. That way and you deprecate the other two over time. Example: setName(String name, String DisplayName) This would require both values to be filled out, and since it's overloaded you could

Re: [ANNOUNCE] New Apache NiFi Committer Oleg Zhurakousky

Big congrats! On Mar 15, 2016 8:42 PM, "Michael Moser" wrote: > Yes, welcome Oleg! Your hard work is very much appreciated by everyone. > > -- Mike > > > On Tue, Mar 15, 2016 at 8:22 PM, Matt Burgess wrote: > > > Congratulations! Well deserved. > > > >

Re: [ANNOUNCE] New Apache NiFi Committer Matt Burgess

l > > > as representing the community well in the blogosphere and twitterverse. > > > We're delighted to have him on board as a committer now! > > > > > > Tony > > > -- Ricky Saltzer http://www.cloudera.com

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

on guidance can be found here: > > https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance > > > > The vote will be open for 96 hours (24 extra hours due to late Friday > > release candidate) > > Please download the release candidate and evaluate the necessary items > > including checking hashes, signatures, build from source, and test. The > > please vote: > > > > [ ] +1 Release this package as nifi-0.5.0 > > [ ] +0 no opinion > > [ ] -1 Do not release this package because because... > > > -- Ricky Saltzer http://www.cloudera.com

Re: Are we thinking about Penalization all wrong?

whether or not to penalize when building a > >> processor. It is based on what the developer will > >>> think may make sense, but in reality DFM's sometimes want to penalize > >> things when the processor doesn't behave that way. > >>> > >>> I'm wondering if it doesn't make sense to remove the concept of > >> penalization all together from Processors and instead > >>> move the Penalty Duration so that it's a setting on the Connection. I > >> think this would clear up the confusion and give the DFM > >>> more control over when/how long to penalize. Could set to the default > to > >> 30 seconds for self-looping connections and no penalization > >>> for other connections. > >>> > >>> Any thoughts? > >>> > >>> Thanks > >>> -Mark > >> > >> > > -- Ricky Saltzer http://www.cloudera.com

Re: Are we thinking about Penalization all wrong?

this today by creating a retry loop using UpdateAttribute and > > RouteOnAttribute [1]. > > > > [1] > > > https://cwiki.apache.org/confluence/download/attachments/57904847/Retry_Count_Loop.xml?version=1=1433271239000=v2 > > > > > > On Thu, Jan 28, 2016 at 1:24 PM

Re: State Management

nfigurable value, > defaulting to /nifi > This way, admins can easily configure it and that way they could view > whats in there, etc. > out-of-band of NiFi. Though I'm all ears if there's a better way of doing > this. > > > > On Dec 31, 2015, at 3:44 PM, Ricky Sa

Re: State Management

Overall this looks great, and will prove very useful as we try to scale nifi out. When in clustered mode, will we have control over which znode the nifi cluster persists to? Or - do we want this unique to the cluster (e.g uuid of the flow)? On Dec 31, 2015 12:35 PM, "Mark Payne"

Re: Input Forbidden Requirement

Aha, that makes sense. Thanks for the explanation! I do agree that it could be useful to have control over when those types of processors execute.

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

will be open for 72 hours. > Please download the release candidate and evaluate the necessary items > including checking hashes, signatures, build from source, and test. > > Then please vote: > > [ ] +1 Release this package as Apache NiFi 0.4.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because... > > > > -- Ricky Saltzer http://www.cloudera.com

Re: [ANNOUNCE] New Apache NiFi PMC Member (and Committer) Sean Busbey

Congrats, Busbey!! On Nov 25, 2015 1:14 PM, "Tony Kurc" wrote: > On behalf of the Apache NiFI PMC, I am very pleased to announce that Sean > Busbey has accepted the PMC's invitation to become a PMC Member and > Committer on the Apache NiFi project. We greatly appreciate all of

Re: [ANNOUNCE] New Apache NiFi Committer Toivo Adams

eatly appreciate all of Toivo's hard work and generous > > contributions to the project. We look forward to his continued > involvement > > in the project. > > > > Welcome, Toivo, and congratulations! > > > -- Ricky Saltzer http://www.cloudera.com

Re: NiFi 0.3 : Query regarding HDFS processor

> it > > into the Hadoop edge node using PutSFTP, followed by PutHDFS. > > But I would like to know if there is any way to directly write the > > FlowFile to HDFS using PutHDFS without writing to Hadoop name node. > > > > Could you please help me to identify the same? > > > > Regards, > > Ramkishan Betta, > > Consultant, BT e-serv India, > > Bengaluru - INDIA > > > > > -- Ricky Saltzer http://www.cloudera.com

Re: [ANNOUNCE] New Apache NiFi Committer Ricky Saltzer

NiFi forward! > > On Wed, Oct 21, 2015 at 3:04 PM Tony Kurc <trk...@gmail.com> wrote: > > > NiFi Community! > > > > Great news! > > > > On behalf of the Apache NiFI PMC, I am very pleased to announce that > Ricky > > Saltzer has accepted the PMC's i

Re: PutHDFS Configuration Issue

> > -- > > View this message in context: > > > http://apache-nifi-developer-list.39713.n7.nabble.com/PutHDFS-Configuration-Issue-tp2998p3003.html > > Sent from the Apache NiFi Developer List mailing list archive at > > Nabble.com. > > > -- Ricky Saltzer http://www.cloudera.com

Re: apache nifi oscon briefing

+1! On Aug 21, 2015 9:04 AM, Ryan Ward ryan.wa...@gmail.com wrote: +1 great demo! On Fri, Aug 21, 2015 at 9:00 AM, Mark Payne marka...@hotmail.com wrote: Definitely a +1 from me. This is a really great talk and well worth the time for those who haven't had a chance to watch it.

Re: [DISCUSS] Feature proposal: First-class Avro Support

/confluence/display/NIFI/First-class+Avro+Support Thanks, Bryan -- Ricky Saltzer http://www.cloudera.com

Re: [DISCUSS] Feature proposal: Read-only mode as default

help avoid accidental movement? Thanks Joe -- Rob -- Ricky Saltzer http://www.cloudera.com

Re: [VOTE] Release Apache NiFi 0.2.1

+1 (non-binding) Hashes, signatures all good Builds, tests run Verified new account functionality On Jul 24, 2015 8:48 AM, Matt Gilman matt.c.gil...@gmail.com wrote: +1 Release this package as nifi-0.2.1 (binding) - Checked signatures and hashes - LICENSE, NOTICE, and README were good -