waitting for your hellp

2017-02-27 Thread sczylbh
Hi, I want to store the data to opentsdb or redis use nifi,Do you have any good suggestions? or can you develop the processor that can put/get data to/from opentsdb or redis.

Re: waitting for your hellp

2017-02-27 Thread Andre
Hi, Writing to OpenTSDB is a reasonably common pattern that can be achieved by: Using OpenTSDB's telnet API together with the PutTCP processor (payload content must be processed to the desired format before reaching PutTCP) or Using OpenTSDB's HTTP REST API together with the InvokeHTTP processo

Re: waitting for your hellp

2017-02-27 Thread Andre
My last message had some residue of copy and paste residues: Where it reads: "Using OpenTSDB's HTTP REST API together with the InvokeHTTP processor (payload content must be processed to the desired format before reaching PutTCP)" it should read "Using OpenTSDB's HTTP REST API together with the

Re: Closing in on a NiFi 0.8.0 release?

2017-02-27 Thread Joe Skora
I think there's a couple considerations related to continuing the 0.x line. First, as JoeW mentioned the Release Line Management page [1] says we support a major release for one year, so we should plan to support 0.7.x for one year from its July 13, 2016 release date [2]. Also, since we considere

Re: Closing in on a NiFi 0.8.0 release?

2017-02-27 Thread Bryan Bende
Joe, Just wanted to clarify that I don't believe the 1.0.0 release was a BETA. There was a 1.0.0-BETA release on 8/5 to gather feedback and testing from the community, and the regular 1.0.0 release on 8/26. http://central.maven.org/maven2/org/apache/nifi/nifi-assembly/1.0.0-BETA/ (8/5) http://c

Re: Closing in on a NiFi 0.8.0 release?

2017-02-27 Thread Joe Witt
Joe 1.0.0 was not a beta release. 1.0.0-beta was a beta release. The intent of the language was we support the old major line for one year once there is a major release. It is of course imperative to respect that folks cannot migrate as quickly as we would always like. But this sort of concern

Re: Closing in on a NiFi 0.8.0 release?

2017-02-27 Thread Joe Skora
Sorry for the confusion regarding 1.0.0-BETA vs 1.0.0, my bad. As for stability, I don't mean build and test stability but real world stability feedback that has led to various repository fixes including the 1.x line transition to the schema based provenance and newly refactored provenance reposit

Re: Testing automation, Deployment in NiFi

2017-02-27 Thread Anshuman Ghosh
Hello Bryan, Greetings of the day! Thank you very much for your reply. I have quickly looked into the documents and we are looking forward for the deployment stuffs that are in development now. However it would be great, if I get some more guidance on the REST API part for testing automation. I

Re: Quick question on LICENSE/NOTICE when bundling controllers and processors

2017-02-27 Thread James Wing
Thank you both for bringing up this discussion. I have a few follow-up questions: 1.) Is it true all of the NAR bundles in the NiFi source should have their own LICENSE and NOTICE files, without exception? In looking through the source, most nifi-*-nar projects have both files for binary depende

Re: Quick question on LICENSE/NOTICE when bundling controllers and processors

2017-02-27 Thread Joe Witt
1) All nars once built do need to contain a LICENSE and NOTICE file to cover what ends up in them as an archive of binary dependencies and also it should cover any specific source dependencies they might have (like MIT javascript libs in nifi-web-ui). 2) We need a LICENSE/NOTICE in every nar. A

Re: Quick question on LICENSE/NOTICE when bundling controllers and processors

2017-02-27 Thread James Wing
Yes, thank you, that does help. I'm slowly sneaking up on an understanding of how it works. James On Mon, Feb 27, 2017 at 1:59 PM, Joe Witt wrote: > 1) All nars once built do need to contain a LICENSE and NOTICE file > to cover what ends up in them as an archive of binary dependencies and > a

Re: Quick question on LICENSE/NOTICE when bundling controllers and processors

2017-02-27 Thread Tony Kurc
Joe, This is awesome and useful - should this guidance go on the wiki somewhere? On Mon, Feb 27, 2017 at 4:59 PM, Joe Witt wrote: > 1) All nars once built do need to contain a LICENSE and NOTICE file > to cover what ends up in them as an archive of binary dependencies and > also it should cover

Re: Quick question on LICENSE/NOTICE when bundling controllers and processors

2017-02-27 Thread James Wing
It may already be in the Licensing Guide ( https://nifi.apache.org/licensing-guide.html). I'll have to read it again to identify net-new material. I'll open a PR if there is. Thanks, James On Mon, Feb 27, 2017 at 4:23 PM, Tony Kurc wrote: > Joe, > This is awesome and useful - should this gui

Need help with Custom Processor

2017-02-27 Thread Pushkara R
Hi, I'm writing a new processor for NiFi which has a dependency on an external library. When I build the NAR and add it to the lib folder and restart NiFi, the external library classes that my processor depends on fail getting loaded with a "ClassNotFound" exception. How do I go about fixing this

Re: Need help with Custom Processor

2017-02-27 Thread Andrew Psaltis
Hi Pushkar, The preferred approach is to add the external dependency to the pom file for your processor. After doing that when you build your nar bundle, the resulting nar file will contain all of the 3rd party dependencies required by your processor. Can you double check that you are indeed includ