Re: Apache NiFi 0.6.1 RC2 Release Helper Guide

2016-04-13 Thread Joe Witt
Team, It was noted that the signatures for the source and convenience binaries uploaded used SHA1 digest. I have uploaded additional signatures for each of the three artifacts that use SHA512. You can validate against these signatures instead or as well using gpg --verbose --verify nifi-0.6.1-s

Re: [VOTE] Incorporate SHA256 part of release process

2016-04-13 Thread Andy LoPresto
Fair enough. OpenSSL is pretty universal, but there are also OS-specific commands to perform the same task. Andy LoPresto alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Apr 13, 2016, at 20:13, Aldrin Piri wrote: > > As far as the wrapper sc

Re: [VOTE] Incorporate SHA256 part of release process

2016-04-13 Thread Aldrin Piri
As far as the wrapper script, I'm in favor of the manual process for the SHA256. The arbitrary shell commands/processes in the Maven build feel too brittle across operating systems and this is multiplied in conjunction with a maintained follow on script(s). Overall would prefer just incurring the

Re: [VOTE] Incorporate SHA256 part of release process

2016-04-13 Thread Andy LoPresto
Tony, That’s definitely a valid concern that I’m sure benefits all release managers to review. The conversation below is regarding the checksums for data integrity only; not the underlying hash used in the GPG signature process. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP

Re: [VOTE] Incorporate SHA256 part of release process

2016-04-13 Thread Tony Kurc
I was under the impression not using SHA-1 WAS part of our release, when we were gpg signing (based off of [1]), which I assumed was the preferred form of assuring an artifact was not "bad". However, it looks like it isn't in our checklist to confirm that SHA-1 wasn't used to make the digital signa

Re: [VOTE] Incorporate SHA256 part of release process

2016-04-13 Thread Andy LoPresto
Obviously a +1 for me. With regard to the plugin not supporting it, can’t Maven execute arbitrary Java/shell commands during build [1]? The issue on MINSTALL has been open since December 2012. I understand we might need a script wrapper to handle cross-platform functionality, but this might be e

Re: [VOTE] Incorporate SHA256 part of release process

2016-04-13 Thread Matt Burgess
+1 > On Apr 13, 2016, at 6:13 PM, Aldrin Piri wrote: > > This was mentioned in the vote thread for the RC2 release and wanted to > separate it out to keep the release messaging streamlined. As mentioned by > Andy, the MD5 and SHA1 are subject to collisions. From another viewpoint, I > like havi

[GitHub] nifi pull request: Nifi 1753 Removed legacy X.509 certificate impl...

2016-04-13 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/346 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enable

[GitHub] nifi pull request: Nifi 1753 Removed legacy X.509 certificate impl...

2016-04-13 Thread alopresto
Github user alopresto commented on the pull request: https://github.com/apache/nifi/pull/346#issuecomment-209713757 Accidentally closed because I had to remove the local branch because of a bad commit order. Copied out, cherry-picked, re-pushed. --- If your project is set up for it,

[GitHub] nifi pull request: Nifi 1753 Removed legacy X.509 certificate impl...

2016-04-13 Thread alopresto
GitHub user alopresto reopened a pull request: https://github.com/apache/nifi/pull/346 Nifi 1753 Removed legacy X.509 certificate implementation references Various logic throughout the application referenced `javax.security.cert.X509Certificate` which is a deprecated class and exist

[GitHub] nifi pull request: Nifi 1753 Removed legacy X.509 certificate impl...

2016-04-13 Thread alopresto
Github user alopresto closed the pull request at: https://github.com/apache/nifi/pull/346 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

Re: [VOTE] Incorporate SHA256 part of release process

2016-04-13 Thread Joe Witt
+1. I should have done it this time. On Wed, Apr 13, 2016 at 9:13 PM, Aldrin Piri wrote: > This was mentioned in the vote thread for the RC2 release and wanted to > separate it out to keep the release messaging streamlined. As mentioned by > Andy, the MD5 and SHA1 are subject to collisions. From

[VOTE] Incorporate SHA256 part of release process

2016-04-13 Thread Aldrin Piri
This was mentioned in the vote thread for the RC2 release and wanted to separate it out to keep the release messaging streamlined. As mentioned by Andy, the MD5 and SHA1 are subject to collisions. From another viewpoint, I like having this as part of the official release process as I typically gene

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

2016-04-13 Thread Matt Burgess
+1 (non-binding) Ran release verifier, checked artifacts, ran in standalone and 1-node cluster (secure and insecure), tried some flows, everything looked fine. > On Apr 12, 2016, at 7:47 PM, Joe Witt wrote: > > Hello Apache NiFi Community, > > I am pleased to be calling this vote for the sou

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

2016-04-13 Thread Andy LoPresto
+1, non-binding. Ran automated release verifier. Checksums, GPG signature, and git commit ID all checked out. (Side note: this may be paranoia, but MD5 and even SHA-1 now have documented pre-collision issues. Can we please add SHA-256 to future releases?) Ran unit tests and contrib-check profil

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

2016-04-13 Thread James Wing
+1. Checked hashes, built from source, ran unit tests. Ran through a simple flow, checked to make sure an issue was resolved (yes!). On Tue, Apr 12, 2016 at 7:47 PM, Joe Witt wrote: > Hello Apache NiFi Community, > > I am pleased to be calling this vote for the source release of Apache > NiFi

[GitHub] nifi pull request: Nifi AWS IoT processors

2016-04-13 Thread KayLerch
Github user KayLerch commented on the pull request: https://github.com/apache/nifi/pull/349#issuecomment-209656778 Hi Joe, thanks for helping me out. I just opened an issue in JIRA => [NIFI-1767](https://issues.apache.org/jira/browse/NIFI-1767) Looking forward to getting t

[GitHub] nifi pull request: Nifi AWS IoT processors

2016-04-13 Thread joewitt
Github user joewitt commented on the pull request: https://github.com/apache/nifi/pull/349#issuecomment-209646256 Hello @KayLerch . Really cool contribution and awesome start. We'll want to make sure there is an open Apache NiFi JIRA for this and you are more than welcome to create

[GitHub] nifi pull request: Nifi AWS IoT processors

2016-04-13 Thread KayLerch
GitHub user KayLerch opened a pull request: https://github.com/apache/nifi/pull/349 Nifi AWS IoT processors [20160413_apache-nifi-aws-iot-pull-request_lerchkay.pdf](https://github.com/apache/nifi/files/217918/20160413_apache-nifi-aws-iot-pull-request_lerchkay.pdf) Four new

Re: Observation regarding PutKafka while implementing NIFI-1672

2016-04-13 Thread Oleg Zhurakousky
Pierre You're absolutely correct. The explanation was valid, but there were problems with the original implementation of how it was described, so that changed, but we didn't update the docs > On Apr 13, 2016, at 16:24, Pierre Villard wrote: > > Hi, > > I was working on NIFI-1672 [1], and wh

Observation regarding PutKafka while implementing NIFI-1672

2016-04-13 Thread Pierre Villard
Hi, I was working on NIFI-1672 [1], and while performing some tests with a local running Kafka instance, I noticed there is a possible error regarding how the behavior of the processor is documented. The "Message delimiter" property is documented with: "Specifies the delimiter (interpreted in it

Re: NPE in PutKafka processors

2016-04-13 Thread McDermott, Chris Kevin (MSDU - STaTS/StorefrontRemote)
Here is a probable patch. I’ve tested it and it seems to do the trick. diff --git a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/PutKafka.java b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/proc

[GitHub] nifi-minifi pull request: MINIFI-15 Created a config file format w...

2016-04-13 Thread JPercivall
GitHub user JPercivall opened a pull request: https://github.com/apache/nifi-minifi/pull/8 MINIFI-15 Created a config file format with documentation, and a Util… … class to transform prospective config.yml into flow.xml and nifi.properties You can merge this pull request into a

[GitHub] nifi-minifi pull request: MINIFI-2 Created a Util class to transfo...

2016-04-13 Thread JPercivall
Github user JPercivall closed the pull request at: https://github.com/apache/nifi-minifi/pull/1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Re: NPE in PutKafka processors

2016-04-13 Thread Joe Witt
Chris, That line is 'attributes.put(ATTR_DELIMITER, new String(messageContext.getDelimiterBytes(), StandardCharsets.UTF_8));' Therefore it appears to assume there is a delimiter which is not correct and should be guarded. Here is the JIRA for it. In your use case you might be able to get away w

Re: [DISCUSS] From Contributor to Committer

2016-04-13 Thread Joe Witt
Tony, I agree with the points you raise and the completeness of the perspective you share. I do think we should add to that a focus on licensing and legal aspects. - The individual has shown an effort to aid the community in producing release which are consistent with ASF licensing requirements a

NPE in PutKafka processors

2016-04-13 Thread McDermott, Chris Kevin (MSDU - STaTS/StorefrontRemote)
Hi! I’m running a 0.7.0 snapshot version and am running into an NPE with the PutKafka processor. I’m thinking Oleg would be interested in this. java.lang.NullPointerException: null at java.lang.String.(String.java:503) ~[na:1.8.0_45] at org.apache.nifi.processors.kafka.PutKafka.buildFailedFlow

Re: NiFi Web UI development in Dreamweaver

2016-04-13 Thread Rob Moran
Colin, Just wanted to echo some of the comments from other responses so far and say welcome. I've been putting together the mockups you see in NIFI-1323 . The initial goal is to modernize a bit for a nice foundation as we plan more key functionality

Re: NiFi Web UI development in Dreamweaver

2016-04-13 Thread Matt Gilman
Colin, Thanks for checking out Apache NiFi. The UI is a packaged as a Java web application that is built as part of NiFi's build process. NiFi uses Maven to build and package the application. You should be able to edit the sources that comprise that WAR with any IDE that can import Maven projects.

Re: NiFi Web UI development in Dreamweaver

2016-04-13 Thread Joe Witt
Colin, I'll defer to others to comment on the specifics around dreamweaver or other tools but I do want to reach out and suggest you could also contribute to https://issues.apache.org/jira/browse/NIFI-1323 which is part of the NiFi 1.0.0 efforts and is under active design/discussion and implementa

NiFi Web UI development in Dreamweaver

2016-04-13 Thread Colin Bowdery
Hi All, Can anyone provide any pointers as to how I might be able to develop the NiFi Web UI using a tool such as Dreamweaver? I have been modifying nifi-web-ui-0.6.0-SNAPSHOT.war manually but would really like to use a more professional approach. I also note there are no HTML files in this .wa

Re: catch commit error in OnTrigger to diversify session behaviour

2016-04-13 Thread Matt Burgess
Upon a TitanException in your load() method, you could wrap it in an IOException and re-throw, and rather than print the stack trace, you can catch the IOException in onTrigger() and send to failure. You likely won't want to rollback the session if you're transferring to failure; the user can ch

catch commit error in OnTrigger to diversify session behaviour

2016-04-13 Thread idioma
Hi, I have a custom Apache NiFi processor whose aim is to load a sample graph into Titan Db. I have a load method that creates the graph with a few vertices/edges and commits the transaction (transaction.commit() is wrapped around a try/catch block to catch any TitanException). Inside my On Trigger

Performance Tuning

2016-04-13 Thread dale.chang13
I'm running Nifi on a Linux VM cluster with 1 NCM and 2 nodes, each with 10 GB. Additionally, I followed through with some of the steps outlined in this link: https://community.hortonworks.com/articles/7882/hdfnifi-best-practices-for-setting-up-a-high-perfo.html for performance Here's my departur

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

2016-04-13 Thread Aldrin Piri
+1, binding Build and tests worked on OS X, CentOS 7, and Windows 7. Verified things were passing on Travis build. Re-ran some flow templates from reviews from some of the associated issues with anticipated results. Verified hashes and signatures. On Wed, Apr 13, 2016 at 7:04 AM, Pierre Villar

[GitHub] nifi pull request: Initial AngularJS application bootstrapping and...

2016-04-13 Thread apiri
Github user apiri commented on the pull request: https://github.com/apache/nifi/pull/331#issuecomment-209457190 Could we get a JIRA established (https://issues.apache.org/jira/browse/NIFI) to track these efforts? With things that seem to be as transformative as this it would be nice

[GitHub] nifi pull request: Adding requirejs, angularjs and its dependencie...

2016-04-13 Thread mcgilman
Github user mcgilman commented on the pull request: https://github.com/apache/nifi/pull/331#issuecomment-209420782 @scottyaslan Looks like you need to update the `apache-rat-plugin` configuration to exclude [1] the angular stuff that's been introduced. Let me know if you have any ques

[GitHub] nifi pull request: NIFI-1724 Added properties to configure log lev...

2016-04-13 Thread pvillard31
GitHub user pvillard31 opened a pull request: https://github.com/apache/nifi/pull/348 NIFI-1724 Added properties to configure log level when file not found and permission denied on FetchFile processor You can merge this pull request into a Git repository by running: $ git pul

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

2016-04-13 Thread Pierre Villard
+1 (non-binding) Ran through the helper release guide. Maven build with tests and contrib-check OK on Windows 10. Tested some flow, everything looks OK. Pierre 2016-04-13 4:47 GMT+02:00 Joe Witt : > Hello Apache NiFi Community, > > I am pleased to be calling this vote for the source release of

[GitHub] nifi pull request: NIFI-1755 Fixed remote process group status cou...

2016-04-13 Thread pvillard31
GitHub user pvillard31 opened a pull request: https://github.com/apache/nifi/pull/347 NIFI-1755 Fixed remote process group status counts by only considering connected remote ports You can merge this pull request into a Git repository by running: $ git pull https://github.com/