Re: [DISCUSS] Closing in on the Apache NiFi 0.7.0 Release

2016-06-15 Thread Tony Kurc
I remember the thread, but it seems I need to reread the thread - honestly the comment did take me by surprise, I think we may have used a few terms that were left open to interpretation. On Jun 15, 2016 5:06 PM, "Joe Skora" wrote: > I agree with Tony on this. > > The point of release branching,

[GitHub] nifi issue #475: NIFI-2026 - Add Maven profile to compile nifi-hadoop-librar...

2016-06-15 Thread trixpan
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/475 @mattyb149 the challenge with settings.xml is that it will still not solve the issue that requires the vendor specific profile, the java arg. But leaving the arg aside (I agree that is very ve

[GitHub] nifi pull request #475: NIFI-2026 - Add Maven profile to compile nifi-hadoop...

2016-06-15 Thread trixpan
Github user trixpan commented on a diff in the pull request: https://github.com/apache/nifi/pull/475#discussion_r67180034 --- Diff: nifi-nar-bundles/nifi-hadoop-libraries-bundle/nifi-hadoop-libraries-nar/pom.xml --- @@ -21,19 +21,70 @@ true true

Re: [DISCUSS] Closing in on the Apache NiFi 0.7.0 Release

2016-06-15 Thread Joe Skora
I agree with Tony on this. The point of release branching, etc. is to make it possible to maintain an older version while building the newer version. Yes, it is a nuisance, but not nearly as much as a new version is for users if it is has significant changes and/or bugs. Except in cases where th

[GitHub] nifi issue #458: NIFI-1829 - Create new DebugFlow processor.

2016-06-15 Thread trkurc
Github user trkurc commented on the issue: https://github.com/apache/nifi/pull/458 I don't mind even a little! Thanks @mosermw --- 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 ena

Re: [DISCUSS] Closing in on the Apache NiFi 0.7.0 Release

2016-06-15 Thread Joe Percivall
Team, There was a lot of great progress yesterday, we closed or pushed 6 tickets. Also two tickets were added that are either critical or finishing shortly. The status of the remaining 12 tickets are below: - "Corrupted flow file leads to a wedged flow" NIFI-2015[1] Added yesterday. Christophe

[GitHub] nifi issue #458: NIFI-1829 - Create new DebugFlow processor.

2016-06-15 Thread mosermw
Github user mosermw commented on the issue: https://github.com/apache/nifi/pull/458 I will review. --- 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 th

[GitHub] nifi issue #458: NIFI-1829 - Create new DebugFlow processor.

2016-06-15 Thread JPercivall
Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/458 @trkurc ok, in order to get 0.7.0 as soon as possible, would you mind if another committer took over reviewing? --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] nifi issue #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP processor

2016-06-15 Thread taftster
Github user taftster commented on the issue: https://github.com/apache/nifi/pull/272 I can try to look at it tonight. But no problems if you want to step in. > On Jun 15, 2016, at 10:51 AM, Joe Percivall wrote: > > @taftster will you have time to finish up this revi

[GitHub] nifi issue #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP processor

2016-06-15 Thread JPercivall
Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/272 @taftster will you have time to finish up this review for 0.7.0 or do you want me to finish it? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHu

[GitHub] nifi pull request #475: NIFI-2026 - Add Maven profile to compile nifi-hadoop...

2016-06-15 Thread trixpan
Github user trixpan commented on a diff in the pull request: https://github.com/apache/nifi/pull/475#discussion_r67176674 --- Diff: nifi-nar-bundles/nifi-hadoop-libraries-bundle/nifi-hadoop-libraries-nar/pom.xml --- @@ -21,19 +21,70 @@ true true

[GitHub] nifi issue #475: NIFI-2026 - Add Maven profile to compile nifi-hadoop-librar...

2016-06-15 Thread mattyb149
Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/475 The more I think about this, especially with the inclusion of elements for specific vendors, I tend to agree with the settings.xml approach. Should be easy to describe in a blog post or email to the

[GitHub] nifi pull request #475: NIFI-2026 - Add Maven profile to compile nifi-hadoop...

2016-06-15 Thread trixpan
Github user trixpan commented on a diff in the pull request: https://github.com/apache/nifi/pull/475#discussion_r67174434 --- Diff: nifi-assembly/pom.xml --- @@ -470,6 +470,15 @@ language governing permissions and limitations under the License. -->

[GitHub] nifi pull request #475: NIFI-2026 - Add Maven profile to compile nifi-hadoop...

2016-06-15 Thread mattyb149
Github user mattyb149 commented on a diff in the pull request: https://github.com/apache/nifi/pull/475#discussion_r67174016 --- Diff: nifi-nar-bundles/nifi-hadoop-libraries-bundle/nifi-hadoop-libraries-nar/pom.xml --- @@ -21,19 +21,70 @@ true true

[GitHub] nifi issue #458: NIFI-1829 - Create new DebugFlow processor.

2016-06-15 Thread trkurc
Github user trkurc commented on the issue: https://github.com/apache/nifi/pull/458 It looks like the issues I had were addressed, but I won't have a chance to dive in deeper until Saturday, maybe --- If your project is set up for it, you can reply to this email and have your reply ap

[GitHub] nifi issue #458: NIFI-1829 - Create new DebugFlow processor.

2016-06-15 Thread trkurc
Github user trkurc commented on the issue: https://github.com/apache/nifi/pull/458 Not until this weekend On Jun 15, 2016 4:30 PM, "Joe Percivall" wrote: > @jskora rebased and addressed comments, > @trkurc are you

[GitHub] nifi issue #458: NIFI-1829 - Create new DebugFlow processor.

2016-06-15 Thread JPercivall
Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/458 @jskora rebased and addressed comments, @trkurc are you able to finish reviewing this for 0.7.0? --- If your project is set up for it, you can reply to this email and have your reply appear on GitH

[GitHub] nifi issue #257: NIFI-1537 Added SNMP processors

2016-06-15 Thread olegz
Github user olegz commented on the issue: https://github.com/apache/nifi/pull/257 @pvillard31 could you please rebase and fix merge conflicts one last time. I am now committed to review/test it so we can have it in 0.7. --- If your project is set up for it, you can reply to this emai

[GitHub] nifi issue #252: NIFI-615 - Create a processor to extract WAV file character...

2016-06-15 Thread JPercivall
Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/252 Gonna review this for potential inclusion in 0.7.0. There are merge conflicts, @jskora can you rebase it? --- If your project is set up for it, you can reply to this email and have your rep

[GitHub] nifi pull request #530: NIFI-1992: Updated site-to-site client and server to...

2016-06-15 Thread markap14
GitHub user markap14 opened a pull request: https://github.com/apache/nifi/pull/530 NIFI-1992: Updated site-to-site client and server to support clustered nifi instances NIFI-1992: Updated site-to-site client and server to support clustered nifi instances. Tested: - 0.

Re: ListenHTTP Questions

2016-06-15 Thread Mark Payne
Dale, You can certainly push to ListenHTTP from NodeJS or curl, or whatever other mechanism you want to use to do POST requests. The fact that you are able to connect from specific nodes sounds like you have some sort of Firewall / Hypervisor in the way. Thanks -Mark > On Jun 15, 2016, at 7:2

[GitHub] nifi pull request #519: NIFI-1996: Fixed bug in the generation of UUID's for...

2016-06-15 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/519 --- 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 #256: NIFI-1578: Create PutSlack processor

2016-06-15 Thread mattyb149
Github user mattyb149 commented on a diff in the pull request: https://github.com/apache/nifi/pull/256#discussion_r67162014 --- Diff: nifi-nar-bundles/nifi-slack-bundle/nifi-slack-processors/src/main/java/org/apache/nifi/processors/slack/PutSlack.java --- @@ -0,0 +1,243 @@ +/*

[GitHub] nifi issue #519: NIFI-1996: Fixed bug in the generation of UUID's for compon...

2016-06-15 Thread olegz
Github user olegz commented on the issue: https://github.com/apache/nifi/pull/519 +1, merging --- 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 fea

[GitHub] nifi issue #520: NIFI-1997: Use the 'autoResumeState' property defined in ni...

2016-06-15 Thread olegz
Github user olegz commented on the issue: https://github.com/apache/nifi/pull/520 Also, looking at #519 it appears that this PR sits on top of #519, correct? --- 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

[GitHub] nifi issue #520: NIFI-1997: Use the 'autoResumeState' property defined in ni...

2016-06-15 Thread olegz
Github user olegz commented on the issue: https://github.com/apache/nifi/pull/520 Aside from that dead default constructor I am ok to merge it. Let me know if you feel like removing it as part of this effort. --- If your project is set up for it, you can reply to this email and have

[GitHub] nifi pull request #520: NIFI-1997: Use the 'autoResumeState' property define...

2016-06-15 Thread olegz
Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/520#discussion_r67159721 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-cluster-protocol/src/main/java/org/apache/nifi/cluster/protocol/jaxb/message/AdaptedDat

[GitHub] nifi pull request #522: NIFI-2000: Ensure that if we override setters in App...

2016-06-15 Thread olegz
Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/522#discussion_r67159525 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/api/FlowFileQueueResource.java --- @@ -71

[GitHub] nifi pull request #522: NIFI-2000: Ensure that if we override setters in App...

2016-06-15 Thread olegz
Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/522#discussion_r67159381 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/api/ControllerResource.java --- @@ -554,6

[GitHub] nifi issue #511: NIFI-1850 - JSON-to-JSON Schema Converter Editor

2016-06-15 Thread olegz
Github user olegz commented on the issue: https://github.com/apache/nifi/pull/511 @YolandaMDavis While I believe it looks good, I think someone from the web team has to look at it as well --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] nifi issue #477: NIFI-1663: Add ConvertAvroToORC processor

2016-06-15 Thread mattyb149
Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/477 Just updated the POM to use Orc 1.1.1 (and changed the hard-coded version to a property) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as wel

[GitHub] nifi pull request #511: NIFI-1850 - JSON-to-JSON Schema Converter Editor

2016-06-15 Thread olegz
Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/511#discussion_r67157791 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-jolt-transform-json-ui/src/main/java/org/apache/nifi/web/util/CustomUIUtils.java --- @@ -0,0 +1,88 @@ +/

[GitHub] nifi pull request #475: NIFI-2026 - Add Maven profile to compile nifi-hadoop...

2016-06-15 Thread mattyb149
Github user mattyb149 commented on a diff in the pull request: https://github.com/apache/nifi/pull/475#discussion_r67157439 --- Diff: nifi-assembly/pom.xml --- @@ -470,6 +470,15 @@ language governing permissions and limitations under the License. -->

[GitHub] nifi pull request #511: NIFI-1850 - JSON-to-JSON Schema Converter Editor

2016-06-15 Thread olegz
Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/511#discussion_r67157240 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/StandardNiFiWebConfigurationContext.java ---

[GitHub] nifi pull request #511: NIFI-1850 - JSON-to-JSON Schema Converter Editor

2016-06-15 Thread olegz
Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/511#discussion_r67156788 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/StandardNiFiWebConfigurationContext.java ---

[GitHub] nifi pull request #511: NIFI-1850 - JSON-to-JSON Schema Converter Editor

2016-06-15 Thread olegz
Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/511#discussion_r67156509 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/StandardNiFiWebConfigurationContext.java ---

[GitHub] nifi pull request #515: NIFI-826 [REVIEW ONLY] Initial commit for determinis...

2016-06-15 Thread olegz
Github user olegz closed the pull request at: https://github.com/apache/nifi/pull/515 --- 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 enabled

Re: ListenHTTP Questions

2016-06-15 Thread dale.chang13
Weird... So we do not have telnet, but I tried again and it worked successfully, but only within the same cluster (VMs that the worker nodes are running on). Performing a curl from the VM that contains the ncm yields a "curl: (7) couldn't connect to host". Likewise for performing a curl from other

[GitHub] nifi issue #328: NIFI-1690 Changed MonitorMemory to use allowable values for...

2016-06-15 Thread olegz
Github user olegz commented on the issue: https://github.com/apache/nifi/pull/328 @alopresto all is addressed. Let me know. --- 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 enable

[GitHub] nifi pull request #328: NIFI-1690 Changed MonitorMemory to use allowable val...

2016-06-15 Thread olegz
Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/328#discussion_r67150175 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-reporting-tasks/src/main/java/org/apache/nifi/controller/MonitorMemory.java --- @@ -154,30 +164,21

[GitHub] nifi pull request #328: NIFI-1690 Changed MonitorMemory to use allowable val...

2016-06-15 Thread olegz
Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/328#discussion_r67149972 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-reporting-tasks/src/main/java/org/apache/nifi/controller/MonitorMemory.java --- @@ -154,30 +164,21

[GitHub] nifi pull request #328: NIFI-1690 Changed MonitorMemory to use allowable val...

2016-06-15 Thread olegz
Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/328#discussion_r67149454 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-reporting-tasks/src/main/java/org/apache/nifi/controller/MonitorMemory.java --- @@ -91,12 +92,21 @@

[GitHub] nifi pull request #328: NIFI-1690 Changed MonitorMemory to use allowable val...

2016-06-15 Thread olegz
Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/328#discussion_r67149312 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-reporting-tasks/src/main/java/org/apache/nifi/controller/MonitorMemory.java --- @@ -154,30 +164,21

[GitHub] nifi pull request #328: NIFI-1690 Changed MonitorMemory to use allowable val...

2016-06-15 Thread olegz
Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/328#discussion_r67149210 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-reporting-tasks/src/main/java/org/apache/nifi/controller/MonitorMemory.java --- @@ -154,30 +164,21

[GitHub] nifi issue #527: NIFI-2009 removed 'annotationData' and 'validationContextFa...

2016-06-15 Thread olegz
Github user olegz commented on the issue: https://github.com/apache/nifi/pull/527 @pvillard31 all done. Thanks! --- 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

[GitHub] nifi issue #475: NIFI-2026 - Add Maven profile to compile nifi-hadoop-librar...

2016-06-15 Thread trixpan
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/475 @mattyb149 latest version should hopefully address the missing `java.arg.15` issue. The new profile is also more inclusive and now allows users to build against MapR or CDH using -Dhadoop.vers

[GitHub] nifi issue #527: NIFI-2009 removed 'annotationData' and 'validationContextFa...

2016-06-15 Thread pvillard31
Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/527 LGTM +1. Do you mind fixing the import auto-ordering? --- 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 th

[GitHub] nifi pull request #529: NIFI-2028: Fixed Site-to-Site Transit URI

2016-06-15 Thread ijokarumawak
GitHub user ijokarumawak opened a pull request: https://github.com/apache/nifi/pull/529 NIFI-2028: Fixed Site-to-Site Transit URI Please review and merge if it looks ok. I've added unit tests and also did IT test to check https and proxy works without problem. Transit U

<    1   2