Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r67982895
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/554
I'm going to rebase, squash, and re-push.
---
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 user alopresto commented on the issue:
https://github.com/apache/nifi/pull/554
I fixed an issue in `GetSNMPTest` (a local variable was referenced from
within an inner class, and wasn't declared `final`). I forgot to squash it with
the commit that closed the PR. It was commit
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/557
---
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 user scottyaslan commented on the issue:
https://github.com/apache/nifi/pull/559
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
Andre,
The proposed processors all sound like nice functionality. I did have a
couple of questions.
Concerning the ParseKV, are you aware of the getDelimitedField[1] function
in Expression Language? I think this may take care of this case for
handling these items.
With the QueryBulkWhois API,
I'm trying to get the 0.7.0 NiFi to start on boot on linux/centos 7.
During all this, I've noticed 0.6.1 doesn't quite work either, left some
notes at the bottom about that.
*For 0.7.0:*
*I followed the modified install commands for the nifi.sh script:*
I untar'd it in:
#/opt/nifi/current ->
Github user miquillo commented on the issue:
https://github.com/apache/nifi/pull/362
@jvwing Thanks for picking this up!
- I would 100% apply this to the AbstractS3processor. By the time I figured
it myself, I already had implemented it (in the wrong class). Should be easy
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/543
---
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 user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/543
Thanks @olegz, will merge it in
---
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
Hello,
As a follow-up, the PutTCP processor was just merged into the master and 0.x
branches and will be in the 0.7.0 release.
Joe
- - - - - -
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com
On Thursday, June 16, 2016 4:57 PM, Joe Percivall
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/543
Also, for the sake of transparency, we had a discussion offline debating
the various directions to go to handle the "consistent inconsistency" and had
the idea for a way for the user to check a box
Github user olegz commented on the issue:
https://github.com/apache/nifi/pull/543
Ok, consistency wins so a somewhat reluctant +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
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/551
---
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 user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/398
---
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 user olegz opened a pull request:
https://github.com/apache/nifi/pull/554
NIFI-2032 port for 0.x
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/olegz/nifi NIFI-2032-0.x
Alternatively you can review and apply these
It looks like the StoreInKiteDataset processor is the issue. It has read 1.85
MB in, but written 0 B out. What are the back pressure settings on that
processor?
Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
Couple of things to notice just from the screenshot...
As Andy points out the store in kite dataset processor appears to be
doing very little. The preceding two processors are
ConvertJSONtoAvro at 270 messages per second. The resulting data is
far smaller than the input which is interesting.
GitHub user alopresto opened a pull request:
https://github.com/apache/nifi/pull/551
Removed duplicate dependency declaration from nifi-standard-processorâ¦
â¦s/pom.xml.
Simple PR for duplicated dependency declaration (probably a copy/paste
error). Did not open Jira for
Hi there, I am seeing huge delays in ConvertJSONToAvro processor where the
converted data trickles down to the next step.Please see attachment.I have
increased the concurrent tasks =100. Is there anything else I can
configure/tune up.
nifi_Capture.PNG
Thanks Andy, but I see ConvertJSONToAvro read 680MB and wrote 2.86MB to
disk in ConvertJSONToAvro, is it not true ?
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.nabble.com/ConvertJSONToAvro-processor-is-slow-tp11957p11960.html
Sent from the Apache NiFi
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/551
Merged in master, 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
Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/553
Some screen shoots of testing update on vagrant vm
GitHub user pvillard31 opened a pull request:
https://github.com/apache/nifi/pull/552
NIFI-2066 dynamic port allocation in SNMP processors unit tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pvillard31/nifi NIFI-2066
GitHub user YolandaMDavis opened a pull request:
https://github.com/apache/nifi/pull/553
NIFI-2063 - correct service installation problems with nifi-env.sh
Made changes to ensure proper execution of nifi.sh install:
1) added cp command of nifi_env.sh to /etc/init.d so it
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/551
Thanks @pvillard31 .
---
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
Yeah, I noticed that as well after sending the message. This could still be
because of back pressure on the Kite processor (if the Kite processor is set to
delay incoming data until it processes a certain amount / the incoming queue is
below a certain threshold, the previous processor will
Github user apiri commented on the issue:
https://github.com/apache/nifi/pull/398
@pvillard31 Sounds fair. Will get this incorporated. Thanks for the
contribution.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user pvillard31 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/496#discussion_r67825492
--- Diff:
nifi-nar-bundles/nifi-enrich-bundle/nifi-enrich-processors/src/main/java/org/apache/nifi/processors/AbstractEnrichProcessor.java
---
@@ -0,0
Github user pvillard31 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/379#discussion_r67956841
--- Diff:
nifi-nar-bundles/nifi-alluxio-bundle/nifi-alluxio-processors/src/main/java/org/apache/nifi/processors/alluxio/AbstractAlluxioProcessor.java
---
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/379
Thanks for the review @apiri!
I still need to take into account some of your comments but I rebased the
PR against master. While doing some additional testing, for a reason I can't
explain yet,
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/556
I'm not sure why but only the main code commit,
236266c9e4ed89b4c78438f36408b5f6e0b0c488, applies to 1.0/master without
problems. The other pom commits do not.
It is easy enough to fix them.
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r67964066
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r67965763
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0 +1,311
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r67965642
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0 +1,311
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r67965881
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0 +1,311
Github user joewitt commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r67966608
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0 +1,311
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/554
I am getting test failures:
```
Results :
Failed tests:
KafkaPublisherTest.validateSuccessfulSendAsDelimited:106 expected:<3> but
was:<-1>
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/555
Nope I am missing it, sorry about that. Once the travis build finishes
successfully I am +1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Hey Joe,
Thanks for the update and taking care of this
Ryan
On Tue, Jun 21, 2016 at 12:22 PM, Joe Percivall <
joeperciv...@yahoo.com.invalid> wrote:
> Hello,
>
>
> As a follow-up, the PutTCP processor was just merged into the master and
> 0.x branches and will be in the 0.7.0 release.
> Joe
>
Github user olegz commented on the issue:
https://github.com/apache/nifi/pull/552
+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
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/523
@scottyaslan Looks great!
The additions made since the initial PR have really improved the
performance of various parts. I've merged this to master.
---
If your project is set up for it,
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/552
---
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 user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/553
@jvwing thanks james for. Makes sense on all fronts. I'm working on an
update now.
---
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 the issue:
https://github.com/apache/nifi/pull/555
In cases where validateWarnWhenPercentThresholdReached fails would
validateWarnWhenSizeThresholdReached fail too? Wondering if we should ignore
both.
---
If your project is set up for it, you can
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/555
NIFI-2067 ignored intermittently failing MemoryTest
left comment with the explanation as to why it was not removed
You can merge this pull request into a Git repository by running:
$ git pull
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/534#discussion_r67970007
--- Diff:
nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-processors/src/main/java/org/apache/nifi/processors/script/InvokeScriptedProcessor.java
---
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r67969885
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/test/java/org/apache/nifi/processors/media/TestExtractMediaMetadata.java
---
@@ -0,0
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/548#discussion_r67957184
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -288,9 +289,13 @@
Github user apiri commented on a diff in the pull request:
https://github.com/apache/nifi/pull/379#discussion_r67958810
--- Diff:
nifi-nar-bundles/nifi-alluxio-bundle/nifi-alluxio-processors/src/main/java/org/apache/nifi/processors/alluxio/GetAlluxio.java
---
@@ -0,0 +1,184 @@
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r67963044
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r67963320
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/523
---
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 user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/548#discussion_r67957067
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -288,9 +289,13 @@
Github user apiri commented on a diff in the pull request:
https://github.com/apache/nifi/pull/379#discussion_r67958464
--- Diff:
nifi-nar-bundles/nifi-alluxio-bundle/nifi-alluxio-processors/src/main/java/org/apache/nifi/processors/alluxio/AbstractAlluxioProcessor.java
---
@@
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r67963557
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0
56 matches
Mail list logo
