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

Github user jskora commented on a diff in the pull request: https://github.com/apache/nifi/pull/458#discussion_r67335284 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/DebugFlow.java --- @@ -0,0 +1,499 @@

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

Github user jskora commented on a diff in the pull request: https://github.com/apache/nifi/pull/458#discussion_r67341980 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/DebugFlow.java --- @@ -0,0 +1,499 @@

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

Github user olegz commented on the issue: https://github.com/apache/nifi/pull/328 @alopresto just fixed it. Took me a while to figure out what's going on but you can read some details here: https://issues.apache.org/jira/browse/NIFI-1730 (last comment). Also, I am now going to have

About Unit Tesing

Hello sir, sir i am working as a tester in one company i want to know about the unit testing on niifi can you send me some document about testing . Thank you

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

Github user jskora commented on the issue: https://github.com/apache/nifi/pull/252 So, the problems you had with the JPG file are two separate issues. - The default `BodyContentHandler` passed to the parser can only handle 100,000 bytes, so any file larger than that produces

[GitHub] nifi pull request #534: Fix for NIFI-1838 & NIFI-1152

Github user pvillard31 commented on a diff in the pull request: https://github.com/apache/nifi/pull/534#discussion_r67423663 --- Diff: nifi-mock/src/main/java/org/apache/nifi/util/MockProcessSession.java --- @@ -793,13 +798,21 @@ private void validateState(final FlowFile flowFile)

Re: [DISCUSS] release line management

JoeS, Understood. Some responses for the points you are raising. --- "At a minimum, everything needed to upgrade from X to Y needs to be explicitly covered in a migration document" Agreed. That is the intent of this document [1] primarily. There is also useful information related to how the

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

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/458 --- 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

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67438723 --- Diff:

Re: putTCP nifi 0.7?

Hello, It is not currently marked as something that will go in 0.7.0 but I will review it to see where it stands. If it is able to be completed shortly (contributor addresses of my feedback) then it will make it in but if not then unfortunately it would slide to a later release. This ticket

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

Github user jskora commented on the issue: https://github.com/apache/nifi/pull/252 Ironically, this boils down to a version dependency conflict between ExtractMediaMetadata which uses Tika 1.7 which uses Drew Noakes' Metadata-Extract 2.6.2 and the existing ExtractImageMetadata which

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

Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/252 Thanks for the updates @jskora, unless if you say otherwise I'm going to assume you're gonna get this knocked out for 0.7.0 as soon as possible. If you think you need more time and can have it

[GitHub] nifi pull request #535: NIFI-2041: Unable to refresh Controller Services whe...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/535 --- 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

[GitHub] nifi pull request #534: Fix for NIFI-1838 & NIFI-1152

Github user pvillard31 commented on a diff in the pull request: https://github.com/apache/nifi/pull/534#discussion_r67424962 --- Diff: nifi-mock/src/test/java/org/apache/nifi/util/TestMockProcessSession.java --- @@ -55,4 +55,35 @@ public void onTrigger(final ProcessContext ctx,

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67435351 --- Diff:

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67439340 --- Diff:

[GitHub] nifi issue #517: NIFI-1994: Fixed issues with controller services and templa...

Github user mcgilman commented on the issue: https://github.com/apache/nifi/pull/517 @markap14 When exporting a template with controller services at multiple levels, it appears the services all end up at the top level group. These should probably retain the same scoping as the source

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67433123 --- Diff: nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-nar/src/main/resources/META-INF/LICENSE --- @@ -0,0 +1,239 @@ + +

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67437336 --- Diff:

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67438756 --- Diff:

[GitHub] nifi pull request #534: Fix for NIFI-1838 & NIFI-1152

Github user PuspenduBanerjee commented on a diff in the pull request: https://github.com/apache/nifi/pull/534#discussion_r67439195 --- Diff: nifi-mock/src/test/java/org/apache/nifi/util/TestMockProcessSession.java --- @@ -55,4 +55,35 @@ public void onTrigger(final ProcessContext

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

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/328 --- 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

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67440149 --- Diff:

[GitHub] nifi pull request #535: NIFI-2041: Unable to refresh Controller Services whe...

GitHub user mcgilman opened a pull request: https://github.com/apache/nifi/pull/535 NIFI-2041: Unable to refresh Controller Services when scoped by Process Group - Fixing issue when attempting to refresh Controller Services when scoped by Process Group. You can merge this pull

[GitHub] nifi pull request #493: NIFI-1037 Created processor that handles HDFS' inoti...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/493 --- 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

[GitHub] nifi issue #493: NIFI-1037 Created processor that handles HDFS' inotify even...

Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/493 @jjmeyer0 LGTM +1 tested with workflows, mvn build OK. Merged in master, but would you mind opening a specific PR for 0.x branch (Java 7 compatible): GetHDFSEvents.java:[208,78] error: local

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67439511 --- Diff:

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

Github user alopresto commented on the issue: https://github.com/apache/nifi/pull/328 Merged and closed. Will do the same for [PR 533](https://github.com/apache/nifi/pull/533). --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67442237 --- Diff:

[GitHub] nifi issue #303: NIFI-1660 - Enhance the expression language with jsonPath f...

Github user apiri commented on the issue: https://github.com/apache/nifi/pull/303 Hey @ckmcd! Looks like we missed the magical incantation to have this closed on the commit. Would you mind closing this when you have the opportunity? Thanks! --- If your project is set up

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67442740 --- Diff:

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67443261 --- Diff:

[GitHub] nifi issue #532: NIFI-1941: Child group contents in exported templates

Github user mcgilman commented on the issue: https://github.com/apache/nifi/pull/532 @jvwing Thanks for jumping in to review! I am not aware of this specific issue though I know we have a number of outside JIRAs surrounding templates and the 1.0.0 release. It doesn't surprise me that

[GitHub] nifi issue #239: Nifi 1540 - AWS Kinesis Get and Put Processors

Github user apiri commented on the issue: https://github.com/apache/nifi/pull/239 Hey @jvwing & @joewitt James, your comment listing the associated JIRA legal issue actually had the nice side effect of getting included in the associated issue. A response is here:

[GitHub] nifi issue #532: NIFI-1941: Child group contents in exported templates

Github user mcgilman commented on the issue: https://github.com/apache/nifi/pull/532 @jvwing Actually, I think I see what the issue is. Going to verify my change and if all looks good, I'll update the PR. --- If your project is set up for it, you can reply to this email and have

[GitHub] nifi issue #532: NIFI-1941: Child group contents in exported templates

Github user mcgilman commented on the issue: https://github.com/apache/nifi/pull/532 @jvwing Just addressed the issue and rebased to current master. --- 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

[GitHub] nifi issue #536: NIFI-1037 Ported processor for HDFS' inotify events to 0.x.

Github user jjmeyer0 commented on the issue: https://github.com/apache/nifi/pull/536 @pvillard31 fixed java 7 issues of this processor as requested. --- 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

[GitHub] nifi pull request #534: Fix for NIFI-1838 & NIFI-1152

Github user PuspenduBanerjee commented on a diff in the pull request: https://github.com/apache/nifi/pull/534#discussion_r67446868 --- Diff: nifi-mock/src/test/java/org/apache/nifi/util/TestMockProcessSession.java --- @@ -36,7 +36,7 @@ public void

[GitHub] nifi pull request #534: Fix for NIFI-1838 & NIFI-1152

Github user PuspenduBanerjee commented on a diff in the pull request: https://github.com/apache/nifi/pull/534#discussion_r67446830 --- Diff: nifi-mock/src/main/java/org/apache/nifi/util/MockProcessSession.java --- @@ -793,13 +798,21 @@ private void validateState(final FlowFile

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67443126 --- Diff:

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67443110 --- Diff:

[GitHub] nifi issue #534: Fix for NIFI-1838 & NIFI-1152

Github user PuspenduBanerjee commented on the issue: https://github.com/apache/nifi/pull/534 @pvillard31 Thanks for your effort to review this. I have incorporated your comments as much as I could. --- If your project is set up for it, you can reply to this email and have your

[GitHub] nifi issue #285: NIFI-1636: Print Stacktrace When Unexpected OnTrigger Excep...

Github user apiri commented on the issue: https://github.com/apache/nifi/pull/285 @rickysaltzer Was combing over PRs in rounding up items for 0.7.0. Curious if the effort highlighted by Oleg makes this particular PR OBE. Thanks! --- If your project is set up for it, you can reply

[GitHub] nifi pull request #506: NIFI-1660 - Enhance the expression language with jso...

Github user ckmcd closed the pull request at: https://github.com/apache/nifi/pull/506 --- 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

[GitHub] nifi pull request #303: NIFI-1660 - Enhance the expression language with jso...

Github user ckmcd closed the pull request at: https://github.com/apache/nifi/pull/303 --- 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

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67440428 --- Diff:

[GitHub] nifi issue #532: NIFI-1941: Child group contents in exported templates

Github user jvwing commented on the issue: https://github.com/apache/nifi/pull/532 I ran through the following steps to test this fix: 1. Confirm the bug a. Built a template on master/1.0 branch with a process group b. Exported the template c. Confirmed that

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67442458 --- Diff:

[GitHub] nifi pull request #397: NIFI-1815

Github user mattyb149 commented on a diff in the pull request: https://github.com/apache/nifi/pull/397#discussion_r67451461 --- Diff: nifi-nar-bundles/nifi-ocr-bundle/nifi-ocr-processors/src/test/resources/tessdata/tessconfigs/nobatch --- @@ -0,0 +1 @@ + --- End diff --

Re: GetJMSQueue does not detect dead connections

I’ll do it. Thanks. Chris McDermott Remote Business Analytics STaTS/StoreFront Remote HPE Storage Hewlett Packard Enterprise Mobile: +1 978-697-5315 https://www.storefrontremote.com On 6/16/16, 3:19 PM, "Oleg Zhurakousky" wrote: >Yes, that is documentation

log event processing

Among all entries, I want to capture some specific log events from the application log and process it continuously. What processor should be used ? -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/log-event-processing-tp11646.html Sent from the Apache NiFi

[GitHub] nifi issue #535: NIFI-2041: Unable to refresh Controller Services when scope...

Github user bbende commented on the issue: https://github.com/apache/nifi/pull/535 +1 looks good --- 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

[GitHub] nifi pull request #534: Fix for NIFI-1838 & NIFI-1152

Github user pvillard31 commented on a diff in the pull request: https://github.com/apache/nifi/pull/534#discussion_r67428396 --- Diff: nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-processors/src/main/java/org/apache/nifi/processors/script/InvokeScriptedProcessor.java ---

[GitHub] nifi issue #532: NIFI-1941: Child group contents in exported templates

Github user jvwing commented on the issue: https://github.com/apache/nifi/pull/532 Reviewing --- 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

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

Github user jskora commented on the issue: https://github.com/apache/nifi/pull/252 Ok, I think I've resolved the problems. The Tika conflict was fixed by udpating Tika and Metadata Extractor dependency versions and adjusting ExtractImageMetadata for new attribute names in the newer

Re: [DISCUSS] release line management

I agree with all those points, but a big +1 to this: > By making any release (incremental, major, or minor) we should be > saying that it is in a mature state and we should certainly be saying > there is no known "loss of capability or risk to their data". For the > examples you provide I

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67438939 --- Diff:

[GitHub] nifi pull request #533: Nifi 1690 0.x

GitHub user olegz opened a pull request: https://github.com/apache/nifi/pull/533 Nifi 1690 0.x You can merge this pull request into a Git repository by running: $ git pull https://github.com/olegz/nifi NIFI-1690-0.x Alternatively you can review and apply these changes as the

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

Github user jskora commented on the issue: https://github.com/apache/nifi/pull/458 Ok, I think that last commit covers the review feedback. --- 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

[GitHub] nifi issue #533: Nifi 1690 0.x

Github user olegz commented on the issue: https://github.com/apache/nifi/pull/533 @alopresto so this is the 0.x port of NIFI-1690 --- 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

Re: About Unit Tesing

Rahul, Here is a section of the developer guide [1] which discusses the testing framework available to developers. [1] https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html#testing Andy LoPresto

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

Github user jskora commented on a diff in the pull request: https://github.com/apache/nifi/pull/458#discussion_r67335539 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/DebugFlow.java --- @@ -0,0 +1,499 @@

[GitHub] nifi pull request #534: Fix for NIFI-1838 & NIFI-1152

GitHub user PuspenduBanerjee opened a pull request: https://github.com/apache/nifi/pull/534 Fix for NIFI-1838 & NIFI-1152 Fix for NIFI-1838 & NIFI-1152 You can merge this pull request into a Git repository by running: $ git pull https://github.com/PuspenduBanerjee/nifi

[GitHub] nifi pull request #252: NIFI-615 - Create a processor to extract WAV file ch...

Github user jskora commented on a diff in the pull request: https://github.com/apache/nifi/pull/252#discussion_r67387964 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/test/java/org/apache/nifi/processors/media/TestExtractMediaMetadata.java --- @@ -0,0

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

Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/272 It should be OK, let me know if not. --- 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

[GitHub] nifi pull request #534: Fix for NIFI-1838 & NIFI-1152

Github user pvillard31 commented on a diff in the pull request: https://github.com/apache/nifi/pull/534#discussion_r67390898 --- Diff: nifi-mock/src/test/java/org/apache/nifi/util/TestMockProcessSession.java --- @@ -16,6 +16,9 @@ */ package org.apache.nifi.util;

[GitHub] nifi pull request #534: Fix for NIFI-1838 & NIFI-1152

Github user pvillard31 commented on a diff in the pull request: https://github.com/apache/nifi/pull/534#discussion_r67391289 --- Diff: nifi-mock/src/test/java/org/apache/nifi/util/TestMockProcessSession.java --- @@ -36,7 +36,7 @@ public void testPenalizeFlowFileFromProcessor() {

Re: GetJMSQueue does not detect dead connections

Chris Given that we are deprecating Get/PutJMS* in favor of Publish/SubscribeJMS, I’d suggest start using those once. Cheers Oleg > On Jun 16, 2016, at 1:34 PM, McDermott, Chris Kevin (MSDU - > STaTS/StorefrontRemote) wrote: > > Folks, > > I’ve been trying to

[GitHub] nifi pull request #534: Fix for NIFI-1838 & NIFI-1152

Github user pvillard31 commented on a diff in the pull request: https://github.com/apache/nifi/pull/534#discussion_r67392290 --- Diff: nifi-mock/src/test/java/org/apache/nifi/util/TestMockProcessSession.java --- @@ -55,4 +55,35 @@ public void onTrigger(final ProcessContext ctx,

[GitHub] nifi pull request #256: NIFI-1578: Create PutSlack processor

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

[GitHub] nifi pull request #252: NIFI-615 - Create a processor to extract WAV file ch...

Github user jskora commented on a diff in the pull request: https://github.com/apache/nifi/pull/252#discussion_r67387942 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java --- @@ -0,0 +1,276

GetJMSQueue does not detect dead connections

Folks, I’ve been trying to test my GetJMSQueue configuration so that it detects a dead broker connection and fails over to an alternate broker. When I say dead connection I mean TCP connection that has not been closed but is no longer passing traffic. In the real world this typically happens

[GitHub] nifi pull request #534: Fix for NIFI-1838 & NIFI-1152

Github user pvillard31 commented on a diff in the pull request: https://github.com/apache/nifi/pull/534#discussion_r67390513 --- Diff: nifi-mock/src/main/java/org/apache/nifi/util/MockProcessSession.java --- @@ -587,13 +589,15 @@ public void transfer(final FlowFile flowFile, final

Attribute for current Processor/Connection

Hi, Is there any attribute available on every flow that will give details on what was the last processor that processed the flow ? I have a flow where I am routing all failures to a single process group for error handling. It will be convenient to have an attribute for current processor, so

Re: Attribute for current Processor/Connection

Hello We do not automatically tag the flow file attributes with sourcing information. That is captured in the provenance trail though. For your case you might consider adding an update attribute processor after each transition point where you want to capture something of interest so you can tag

RE: Attribute for current Processor/Connection

Thanks Joe for quick response. I agree it can be implemented with either of the approach you suggested. But both approaches are more cumbersome to implement. Do you think it will be worth to explore adding such an attribute ? I think it will be of value to other developers also during

[GitHub] nifi pull request #252: NIFI-615 - Create a processor to extract WAV file ch...

Github user jskora commented on a diff in the pull request: https://github.com/apache/nifi/pull/252#discussion_r67383325 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java --- @@ -0,0 +1,276

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

Github user mosermw commented on the issue: https://github.com/apache/nifi/pull/458 Completed review, latest changes look good, unit testing and integration testing worked as expected, code passes -Pcontrib-check. +1 I will squash commits and merge to 0.x and master shortly.

[GitHub] nifi pull request #252: NIFI-615 - Create a processor to extract WAV file ch...

Github user jskora commented on a diff in the pull request: https://github.com/apache/nifi/pull/252#discussion_r67384364 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java --- @@ -0,0 +1,276

[GitHub] nifi pull request #252: NIFI-615 - Create a processor to extract WAV file ch...

Github user jskora commented on a diff in the pull request: https://github.com/apache/nifi/pull/252#discussion_r67385461 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java --- @@ -0,0 +1,276

putTCP nifi 0.7?

Will this one make 0.7? https://issues.apache.org/jira/browse/NIFI-1834

[GitHub] nifi pull request #534: Fix for NIFI-1838 & NIFI-1152

Github user PuspenduBanerjee commented on a diff in the pull request: https://github.com/apache/nifi/pull/534#discussion_r67394024 --- Diff: nifi-mock/src/main/java/org/apache/nifi/util/MockProcessSession.java --- @@ -793,13 +798,21 @@ private void validateState(final FlowFile

[GitHub] nifi pull request #534: Fix for NIFI-1838 & NIFI-1152

Github user PuspenduBanerjee commented on a diff in the pull request: https://github.com/apache/nifi/pull/534#discussion_r67394594 --- Diff: nifi-mock/src/test/java/org/apache/nifi/util/TestMockProcessSession.java --- @@ -36,7 +36,7 @@ public void

[GitHub] nifi pull request #252: NIFI-615 - Create a processor to extract WAV file ch...

Github user jskora commented on a diff in the pull request: https://github.com/apache/nifi/pull/252#discussion_r67393537 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java --- @@ -0,0 +1,276

[GitHub] nifi pull request #534: Fix for NIFI-1838 & NIFI-1152

Github user PuspenduBanerjee commented on a diff in the pull request: https://github.com/apache/nifi/pull/534#discussion_r67393509 --- Diff: nifi-mock/src/main/java/org/apache/nifi/util/MockProcessSession.java --- @@ -587,13 +589,15 @@ public void transfer(final FlowFile flowFile,

Re: GetJMSQueue does not detect dead connections

Thanks, Oleg. Do you have an example of how to configure the JMSConnectionFactoryProvider to work with AMQ? The documentation says that the MQ Client Libraries path is optional with org.apache.activemq.ActiveMQConnectionFactory but I am find that is not the case. Thanks, Chris McDermott

Re: GetJMSQueue does not detect dead connections

So does that mean that I cannot use the AMQ client packaged with NiFi but rather provide my own? Sorry if I an being obtuse. Chris McDermott Remote Business Analytics STaTS/StoreFront Remote HPE Storage Hewlett Packard Enterprise Mobile: +1 978-697-5315 https://www.storefrontremote.com On

Re: GetJMSQueue does not detect dead connections

Chris That is correct. The idea was to make sure that we can support multiple clients and multiple vendors since Get/Put only supported AMQP and only one version. The new JMS support allows you to use any JMS vendor and the only extra work we are asking you to do is to provide

Re: GetJMSQueue does not detect dead connections

Oleg - so to Chris' other comment about docs suggesting the ActiveMQ lib path is not needed - is that a doc bug? On Thu, Jun 16, 2016 at 3:13 PM, Oleg Zhurakousky wrote: > Chris > > That is correct. > The idea was to make sure that we can support multiple clients

Re: GetJMSQueue does not detect dead connections

Yes, that is documentation bug. Chris would you mind raising a JIRA or I can do it. Cheers Oleg > On Jun 16, 2016, at 3:15 PM, Joe Witt wrote: > > Oleg - so to Chris' other comment about docs suggesting the ActiveMQ > lib path is not needed - is that a doc bug? > > On

Re: GetJMSQueue does not detect dead connections

Yes, you can probably look at the test case for it since it uses embedded AMQP. Let m know if you need more help with it. Cheers Oleg > On Jun 16, 2016, at 2:50 PM, McDermott, Chris Kevin (MSDU - > STaTS/StorefrontRemote) wrote: > > Thanks, Oleg. > > Do you have an

[GitHub] nifi pull request #252: NIFI-615 - Create a processor to extract WAV file ch...

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/252#discussion_r67402505 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java --- @@ -0,0

[GitHub] nifi issue #526: NIFI-1952 Create REST endpoints for user/group/policy manag...

Github user jtstorck commented on the issue: https://github.com/apache/nifi/pull/526 @mcgilman I've addressed most of your comments on the PR aside from renaming Group to UserGroup, which I still plan on doing soon. Please take a look at my latest commit on the PR. --- If your

[GitHub] nifi issue #533: Nifi 1690 0.x

Github user apiri commented on the issue: https://github.com/apache/nifi/pull/533 Hey @olegz, Looks like the magic words to close this PR were missed in the commit. Could you please close this when you have a chance? Thanks! --- If your project is set up for it,

[GitHub] nifi pull request #537: NIFI-1955: Deprecate IntegerHolder, LongHolder, Bool...

GitHub user rekhajoshm opened a pull request: https://github.com/apache/nifi/pull/537 NIFI-1955: Deprecate IntegerHolder, LongHolder, BooleanHolder NIFI-1955: Deprecate IntegerHolder, LongHolder, BooleanHolder You can merge this pull request into a Git repository by running: $

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

Github user mcgilman commented on a diff in the pull request: https://github.com/apache/nifi/pull/511#discussion_r67456463 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/pom.xml --- @@ -355,10 +355,5 @@ spock-core

[GitHub] nifi pull request #538: NIFI-1774: AbstractControllerService deprecated anno...

GitHub user rekhajoshm opened a pull request: https://github.com/apache/nifi/pull/538 NIFI-1774: AbstractControllerService deprecated annotation NIFI-1774: AbstractControllerService deprecated annotation You can merge this pull request into a Git repository by running: $ git

[GitHub] nifi pull request #532: NIFI-1941: Child group contents in exported template...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/532 --- 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

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

Github user mcgilman commented on a diff in the pull request: https://github.com/apache/nifi/pull/511#discussion_r67456561 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/StandardNiFiServiceFacade.java --- @@

[GitHub] nifi issue #532: NIFI-1941: Child group contents in exported templates

Github user jvwing commented on the issue: https://github.com/apache/nifi/pull/532 Thanks for tracking that down, it makes sense now that I see your changes. I tested the new changes, did a full build with contrib check (thanks for the earlier fix), and will merge. --- If your

  1   2   >