Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/536
@jjmeyer0 Thanks! I just merged it in 0.x branch.
---
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 f
Github user pvillard31 closed the pull request at:
https://github.com/apache/nifi/pull/401
---
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 en
Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/239
Thanks for noticing that, I didn't realize it would cross-link. That's not
what I was hoping for.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user mans2singh commented on the issue:
https://github.com/apache/nifi/pull/502
Hey @pvillard31 - Thanks for your comments and I will try to address to
your questions below:
1. In order to run integration tests, we need to run apache ignite 1.6
locally (or create the
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 enable
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 proj
GitHub user rekhajoshm opened a pull request:
https://github.com/apache/nifi/pull/539
NIFI-1549: Fix JMSConsumer exception
NIFI-1549: Fix JMSConsumer exception
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rekhajoshm/nifi NIFI-1
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/511
@YolandaMDavis While reading over your PR I noticed that the
ControllerService and ReportingTask URI's in the
StandandNiFiWebConfigurationContext are incorrect. They shouldn't contain the
path segmen
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 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 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 pu
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 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, yo
Github user apiri commented on the issue:
https://github.com/apache/nifi/pull/502
Hey @mans2singh,
A bit late to the game but was doing some scanning over issues and
performing cleanup.
Just curious if any thought was given to treating this as an alternate
implementa
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 enabled
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 enabled
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 --
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 f
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 t
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
re
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 testPenalizeFlowFileFromProcessor(
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 not
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 flow
GitHub user jjmeyer0 opened a pull request:
https://github.com/apache/nifi/pull/536
NIFI-1037 Ported processor for HDFS' inotify events to 0.x.
Ported processor for HDFS' inotify events.
You can merge this pull request into a Git repository by running:
$ git pull https://github
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 not
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 your
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:
https://i
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 user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/525#discussion_r67443261
--- Diff:
nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/src/test/java/org/apache/nifi/processors/windows/event/log/EventSubscr
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/525#discussion_r67443110
--- Diff:
nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/src/test/java/org/apache/nifi/processors/windows/event/log/EvtSubscrib
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/525#discussion_r67443126
--- Diff:
nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/src/test/java/org/apache/nifi/processors/windows/event/log/EvtSubscrib
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/525#discussion_r67442740
--- Diff:
nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/src/test/java/org/apache/nifi/processors/windows/event/log/EvtSubscrib
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/525#discussion_r67442458
--- Diff:
nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/src/test/java/org/apache/nifi/processors/windows/event/log/EvtSubscrib
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/525#discussion_r67442237
--- Diff:
nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/src/test/java/org/apache/nifi/processors/windows/event/log/EventSubscr
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 proc
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/525#discussion_r67440428
--- Diff:
nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/src/main/java/org/apache/nifi/processors/windows/event/log/jna/WEvtApi
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 user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/525#discussion_r67440149
--- Diff:
nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/src/main/java/org/apache/nifi/processors/windows/event/log/EvtSubscrib
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 enable
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/525#discussion_r67439511
--- Diff:
nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/src/main/java/org/apache/nifi/processors/windows/event/log/EvtSubscrib
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/525#discussion_r67439340
--- Diff:
nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/src/main/java/org/apache/nifi/processors/windows/event/log/jna/EventSu
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 ct
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/525#discussion_r67438939
--- Diff:
nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/src/main/java/org/apache/nifi/processors/windows/event/log/EvtSubscrib
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/525#discussion_r67438756
--- Diff:
nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/src/main/java/org/apache/nifi/processors/windows/event/log/EvtSubscrib
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/525#discussion_r67438723
--- Diff:
nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/src/main/java/org/apache/nifi/processors/windows/event/log/EvtSubscrib
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/525#discussion_r67437336
--- Diff:
nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/src/main/java/org/apache/nifi/processors/windows/event/log/EvtSubscrib
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/525#discussion_r67435751
--- Diff:
nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/src/main/java/org/apache/nifi/processors/windows/event/log/EvtSubscrib
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/525#discussion_r67435351
--- Diff:
nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/src/main/java/org/apache/nifi/processors/windows/event/log/EvtSubscrib
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 believe
Github user PuspenduBanerjee commented on a diff in the pull request:
https://github.com/apache/nifi/pull/534#discussion_r67434506
--- Diff:
nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-processors/src/main/java/org/apache/nifi/processors/script/InvokeScriptedProcessor.java
--
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 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 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 enable
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 p
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 feat
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 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 enable
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, fin
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 slide
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 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)
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 u
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 f
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 enable
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 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 req
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 t
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 c
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
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 bug.
>
>Chris would you mind rais
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 Thu, Jun 16, 2016 at 3:1
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 proj
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 and multiple
> vendors since Get
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 ConnectionFactory
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 6
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 +1,2
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 example of how to configu
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
Github user PuspenduBanerjee commented on a diff in the pull request:
https://github.com/apache/nifi/pull/534#discussion_r67395014
--- Diff:
nifi-mock/src/test/java/org/apache/nifi/util/TestMockProcessSession.java ---
@@ -55,4 +55,35 @@ public void onTrigger(final ProcessContext ct
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 testPenalizeFlowFileFromProcessor(
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 flow
Will this one make 0.7?
https://issues.apache.org/jira/browse/NIFI-1834
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 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,
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 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, fin
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 test my GetJMSQueue configura
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() {
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 user pvillard31 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/534#discussion_r67390752
--- Diff:
nifi-mock/src/main/java/org/apache/nifi/util/MockProcessSession.java ---
@@ -793,13 +798,21 @@ private void validateState(final FlowFile flowFile)
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
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
enable
Hi devs,
Just a friendly reminder to please run the “mvn clean install -Pcontrib-check”
command before submitting a PR or merging any code. The contrib-check profile
will run the checkstyle rules and alert on any issues. Twice in the last couple
days minor things have snuck into the master bran
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/252#discussion_r67389343
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0 +1,276 @
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 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 @
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 +1,4
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/252#discussion_r67386979
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/test/java/org/apache/nifi/processors/media/TestExtractMediaMetadata.java
---
@@ -0,0 +1,4
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 NIFI-11
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 @
1 - 100 of 115 matches
Mail list logo
