[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 I've tried to build this locally twice (clean checkouts and everything). It is failing with a compilation error in `MonitorMemoryTest` saying that `UserService` cannot be found. I had to clean up a

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

I added a comment to the JIRA ticket associated with this pull request. I think there should be discussion / buy-in from others on the aestetics of introducing a new processor property for this edge case. Instead, I think the goals of this request could be fulfilled without strictly introducing

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

Github user adamonduty commented on a diff in the pull request: https://github.com/apache/nifi/pull/256#discussion_r67284798 --- 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 pull request #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP pro...

Github user taftster commented on a diff in the pull request: https://github.com/apache/nifi/pull/272#discussion_r67284145 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/InvokeHTTP.java --- @@ -761,24

[GitHub] nifi pull request #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP pro...

Github user taftster commented on a diff in the pull request: https://github.com/apache/nifi/pull/272#discussion_r67283832 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/InvokeHTTP.java --- @@ -215,14

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

Github user adamonduty commented on the issue: https://github.com/apache/nifi/pull/256 @mattyb149 I've squashed and rebased against the latest master. Would be great if you don't mind committing to both master and 0.x. --- If your project is set up for it, you can reply to this

[GitHub] nifi pull request #501: NIFI-1974 - Support Custom Properties in Expression ...

Github user YolandaMDavis commented on a diff in the pull request: https://github.com/apache/nifi/pull/501#discussion_r67282864 --- Diff: nifi-api/src/main/java/org/apache/nifi/registry/FileVariableRegistry.java --- @@ -0,0 +1,70 @@ +/* + * Licensed to the Apache Software

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

Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/256 +1 LGTM, can you squash your commits into 1? should make it easier to rebase (will need to change the version to 0.7.0-SNAPSHOT) unless after you squash you want to issue another PR against 0.x? If

[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_r67281209 --- 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 pull request #532: NIFI-1941: Child group contents in exported template...

GitHub user mcgilman opened a pull request: https://github.com/apache/nifi/pull/532 NIFI-1941: Child group contents in exported templates - Ensuring child group contents are included in exported templates. You can merge this pull request into a Git repository by running: $ git

[GitHub] nifi pull request #255: NIFI-1594: Add option to bulk using Index or Update.

Github user mattyb149 commented on a diff in the pull request: https://github.com/apache/nifi/pull/255#discussion_r67277159 --- Diff: nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/PutElasticsearch.java

Re: NIFI-2026: Opinion needed about adding non-Apache repos

Matt, I left java.args.15 out of my scope as I could not find a reason to use it that not connected to the additional step documented by sumo when running NiFi against MapR's environment. But yes, having java.args.15 replaced by a property would streamline deployment of NiFi where custom args

Re: NIFI-2026: Opinion needed about adding non-Apache repos

OK well let's keep poking at it until we have the best option possible. Will look into sparks approach. Thanks Joe On Jun 15, 2016 8:27 PM, "Andre" wrote: > Joe, > > I wouldn't say I am supportive of it... But you guys have far more > experience in this thing than me, so I

Re: NIFI-2026: Opinion needed about adding non-Apache repos

Joe, I wouldn't say I am supportive of it... But you guys have far more experience in this thing than me, so I am considering all options and trying to keep an open mind. :-) Had it been my choice - and no side effects are caused by the changes - I rather use Spark's approach and have the repos

Re: NIFI-2026: Opinion needed about adding non-Apache repos

Your hadoop.version could also be set by this profile, right? And conceivably hive.version and hbase.version (et al) if all has been set up correctly (and we can change if not, as we should be setting all dependency versions from properties). Do you need the java.arg.15 for this? I think it's

Re: NIFI-2026: Opinion needed about adding non-Apache repos

Andre So are you also supportive of the settings based approach for now? Thanks Joe On Jun 15, 2016 8:08 PM, "Andre" wrote: > Just to complement this conversation. > > I did use the settings.xml (basic changes, specifying profiles with the > appropriate repositories) > >

Re: NIFI-2026: Opinion needed about adding non-Apache repos

Just to complement this conversation. I did use the settings.xml (basic changes, specifying profiles with the appropriate repositories) As initially suspected, the libraries are then added to NARs beyond the nifi-hadoop-libraries-bundle. Using -Pmapr -Dhadoop.version=2.7.0-mapr-1506 results in:

[GitHub] nifi pull request #531: NIFI-2007: Restoring bulletin functionality

GitHub user mcgilman opened a pull request: https://github.com/apache/nifi/pull/531 NIFI-2007: Restoring bulletin functionality - Restoring bulletin functionality. - Ensuring appropriate merging of bulletins in clustered responses. You can merge this pull request into a Git

Re: Content Repository Cleanup Schedule

Hey Mark - Yeah, agreed. I'm moving some of the 15+ day old files out just because this is kind of an emergency. Yeah, that's not exactly "normal", but I have a new pipeline that batches up errors and the FlowFile is basically 0-bytes with attribute information regarding the error so they can be

Re: Content Repository Cleanup Schedule

Deleting the old files could certainly cause some problems. The weird thing is that it shows that you have 10,000+ FlowFiles, each of which is 0 bytes. Is that normal for your flow? Could you try running the following against your content repo: find . -size +1M find . | wc -l Curious how

[GitHub] nifi pull request #248: NIFI-1568: Add Filter Capability to UnpackContent

Github user mattyb149 commented on a diff in the pull request: https://github.com/apache/nifi/pull/248#discussion_r67246009 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/UnpackContent.java --- @@ -154,75

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

Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/272 @taftster I'll let you finish it up tonight if you have time since you've already had eyes on it. If you're not able to, I'll take a look tomorrow. --- If your project is set up for it, you can

Re: Content Repository Cleanup Schedule

Is it safe to manually remove some of the older files in the repository to avoid our disk from filling up? On Wed, Jun 15, 2016 at 4:55 PM, Ricky Saltzer wrote: > Just a reminder, I just today noticed the "archive.enabled" option was > false and changed it to true. > > $

Re: Content Repository Cleanup Schedule

Just a reminder, I just today noticed the "archive.enabled" option was false and changed it to true. $ find . -type f -ls | grep archive | wc -l 0 On Wed, Jun 15, 2016 at 4:53 PM, Mark Payne wrote: > OK, thanks. It doesn't appear that it believes there is anything to >

Re: Content Repository Cleanup Schedule

OK, thanks. It doesn't appear that it believes there is anything to reclaim. Can you try going to your content repository and running: find . -type f -ls | grep archive Curious as to how much data it has archived. > On Jun 15, 2016, at 4:48 PM, Ricky Saltzer wrote: > > Oh

Re: Content Repository Cleanup Schedule

Oh sorry! Trying again [1] https://gist.githubusercontent.com/rickysaltzer/b00196a3881c052df9b38b418722cd02/raw/279a1bc8c60530426732eb7b653de1f3f74574e2/gistfile1.txt On Wed, Jun 15, 2016 at 4:38 PM, Ricky Saltzer wrote: > I should also mention, I just realized that our

Re: Content Repository Cleanup Schedule

It is definitely best to try to keep those in sync, but that won't affect this, as the NCM isn't involved in the nodes' internal maintenance, etc. > On Jun 15, 2016, at 4:38 PM, Ricky Saltzer wrote: > > I should also mention, I just realized that our worker nodes are on

Re: Content Repository Cleanup Schedule

Ricky - can't get to that URL, unfortunately. Tells me "This site can't be reached". May be easier to just copy & paste those particular threads here. Thanks -Mark > On Jun 15, 2016, at 4:36 PM, Ricky Saltzer wrote: > > Looks like the threads are parked and waiting [1] >

Re: Content Repository Cleanup Schedule

I should also mention, I just realized that our worker nodes are on 0.5.1, and for some reason I missed updating the master from 0.4.0. I'm sure that is not helping. On Wed, Jun 15, 2016 at 4:36 PM, Ricky Saltzer wrote: > Looks like the threads are parked and waiting [1] > >

Re: Content Repository Cleanup Schedule

Looks like the threads are parked and waiting [1] [1] http://github.mtv.cloudera.com/gist/ricky/7a5d89f2eeba58e2206d/raw/0e2b446ca049a8b5f27298c700ac709772d2847c/gistfile1.txt On Wed, Jun 15, 2016 at 4:33 PM, Joe Witt wrote: > thanks Ricky - then please take a look at

[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 I set this up to analyze all the files I have in my downloads folder to see what happened and what errors I came across. I found a couple interesting ones. The first should be a

Re: Content Repository Cleanup Schedule

Hey Joe - The NiFi web UI currently reads as: Active threads: 3 Queued: 10,173 / 0 bytes Connected nodes: 2 / 2 Stats last refreshed: 13:31:28 PDT On Wed, Jun 15, 2016 at 4:29 PM, Joe Witt wrote: > And the data remains? If so that is an interesting data point I > think.

Re: Content Repository Cleanup Schedule

I do agree. Unfortunately, I was a bit off, apparently, when I said "an issue a while back." It turns out that the ticket was 1726 [1], which was fixed in 0.6.1. To determine if this is what is biting you, could you do a thread-dump (bin/nifi.sh dump thread-dump.txt) and then look in that file

Re: Content Repository Cleanup Schedule

And the data remains? If so that is an interesting data point I think. So to mark's point how much data do you have queued up actively in the flow then on that nodes? Number of objects you mention is 3273 files corresponding to 825GB in the content repository. Does NiFi see those 825GB worth

Re: Content Repository Cleanup Schedule

I have two nodes in clustered mode. I have the other node that isn't filling up as my primary. I've actually already restarted nifi on the node which has the large repository a few times. On Wed, Jun 15, 2016 at 4:22 PM, Joe Witt wrote: > Ricky, > > If you restart nifi and

Re: Content Repository Cleanup Schedule

Ricky, If you restart nifi and then find that it cleans those things up I believe then it is related to the defects corrected in the 0.5/0.6 timeframe. Is restarting an option for you at this time. You agree mark? Thanks Joe On Wed, Jun 15, 2016 at 4:21 PM, Ricky Saltzer

Re: Content Repository Cleanup Schedule

Hey Mark - Thanks for the quick reply! This is our production system so it's unfortunately running 0.4.0. There are currently 3273 files, with some files dating back to May 18th. The content repository itself is 825G. Ricky On Wed, Jun 15, 2016 at 4:17 PM, Mark Payne

Re: Content Repository Cleanup Schedule

Hey Ricky The reclaim process is pretty much continuous. What version of NiFi are you running? I know there was an issue with this a while back that caused it not to cleanup properly. Also, how much data & how many FlowFiles do you have queued up in your flow? Data won't be archived or

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

Github user olegz commented on the issue: https://github.com/apache/nifi/pull/257 . . . and you almost scored ;) but. . . anyway, will try to wrap it up tomorrow --- 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

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

Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/257 @olegz half-time ;) done! --- 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

Re: [DISCUSS] release line management

Sorry, put this in the wrong thread... In another thread, I put forth the recommendation of a 0.7.1 release, for features that don't make it in 0.7.0, but were intended to (to speed along the 0.7.0 release). As a consumer of NIFI, I still like that idea. Not being part of the dev team, but

Content Repository Cleanup Schedule

Hey guys - I recently discovered I didn't have my "archive.enabled" option set to true after my disk filled up to 95%. I enabled it and then set the retention period to 12 hours and 50% (default values). However, after restarting NiFi, I am not seeing any disk space reclaimed. I'm curious, is

Re: [DISCUSS] release line management

I think any change to reduce support for 0.x should depend on first reaching a mature state with 1.x. Only after the new release is stable can 0.x users upgrade to 1.x without loss of capability or risk to their data. I don't think the guidance needs significant changes, but from an enterprise

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

In another thread, I put forth the recommendation of a 0.7.1 release, for features that don't make it in 0.7.0, but were intended to (to speed along the 0.7.0 release). As a consumer of NIFI, I still like that idea. Not being part of the dev team, but assuming based on their track record, I'm

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

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

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

Github user adamonduty commented on a diff in the pull request: https://github.com/apache/nifi/pull/256#discussion_r67232219 --- 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 pull request #458: NIFI-1829 - Create new DebugFlow processor.

Github user mattyb149 commented on a diff in the pull request: https://github.com/apache/nifi/pull/458#discussion_r67230976 --- 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 mosermw commented on a diff in the pull request: https://github.com/apache/nifi/pull/458#discussion_r67230370 --- 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 mosermw commented on a diff in the pull request: https://github.com/apache/nifi/pull/458#discussion_r67230167 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/DebugFlow.java --- @@ -0,0 +1,499

Re: [DISCUSS] release line management

Yes, I think we need to probably tighten the language to take as much inference (and hence misunderstanding) out as possible. On Jun 15, 2016 5:59 PM, "Joe Witt" wrote: > > > > Tony, Joe, > > It sounds as though you would like to propose a change to this [1] > release line

[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_r67227890 --- Diff: nifi-assembly/NOTICE --- @@ -289,6 +289,11 @@ The following binary components are provided under the Apache Software License v Apache

[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 @JPercivall, I'll try to get this updated tomorrow morning. This was originally done in February, but I'm hoping the rebase won't be too bad. --- If your project is set up for it, you can reply to

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

Github user YolandaMDavis commented on a diff in the pull request: https://github.com/apache/nifi/pull/511#discussion_r67226364 --- 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 #511: NIFI-1850 - JSON-to-JSON Schema Converter Editor

Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/511#discussion_r67223717 --- 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

Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/511#discussion_r67223433 --- 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 #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_r67222856 --- 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 #511: NIFI-1850 - JSON-to-JSON Schema Converter Editor

Github user YolandaMDavis commented on the issue: https://github.com/apache/nifi/pull/511 @olegz thanks for taking a look! as noted above I'll make the changes cited and update this request. --- If your project is set up for it, you can reply to this email and have your reply appear

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

Github user YolandaMDavis commented on a diff in the pull request: https://github.com/apache/nifi/pull/511#discussion_r67222589 --- Diff:

[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_r67222367 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/test/java/org/apache/nifi/processors/media/TestExtractMediaMetadata.java --- @@ -0,0

[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_r67221558 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/test/java/org/apache/nifi/processors/media/TestExtractMediaMetadata.java --- @@ -0,0

[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_r67221005 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/test/java/org/apache/nifi/processors/media/TestExtractMediaMetadata.java --- @@ -0,0

[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_r67218396 --- 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 JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/252#discussion_r67218529 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java --- @@ -0,0

[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_r67218355 --- 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_r67218079 --- 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 JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/252#discussion_r67217364 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/test/java/org/apache/nifi/processors/media/TestExtractMediaMetadata.java --- @@ -0,0

[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_r67216685 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java --- @@ -0,0

[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_r67215325 --- 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 #511: NIFI-1850 - JSON-to-JSON Schema Converter Editor

Github user YolandaMDavis commented on a diff in the pull request: https://github.com/apache/nifi/pull/511#discussion_r67215337 --- Diff:

[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_r67214948 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java --- @@ -0,0

[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_r67213076 --- 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 #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 all done --- 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

[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 Thanks @olegz . If you rebase and squash, I'll verify and merge. --- 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 #328: NIFI-1690 Changed MonitorMemory to use allowable val...

Github user alopresto commented on a diff in the pull request: https://github.com/apache/nifi/pull/328#discussion_r67210183 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-reporting-tasks/src/main/java/org/apache/nifi/controller/MonitorMemory.java --- @@ -154,30

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

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/522 --- 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 #527: NIFI-2009 removed 'annotationData' and 'validationContextFa...

Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/527 @olegz It seems it is in conflict with 0.x branch, could you check if I am wrong and if not submit a PR for 0.x? --- If your project is set up for it, you can reply to this email and have your

[GitHub] nifi pull request #527: NIFI-2009 removed 'annotationData' and 'validationCo...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/527 --- 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 #520: NIFI-1997: Use the 'autoResumeState' property define...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/520 --- 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 #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_r67195219 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java --- @@ -0,0

[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_r67193173 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java --- @@ -0,0

[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_r67193966 --- 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 #522: NIFI-2000: Ensure that if we override setters in Applicatio...

Github user markap14 commented on the issue: https://github.com/apache/nifi/pull/522 @olegz I updated the PR to provide a getter in the ApplicationResource in order to avoid the duplicate instance variable as you suggested. --- If your project is set up for it, you can reply to this

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

Github user markap14 commented on the issue: https://github.com/apache/nifi/pull/520 @olegz I updated the PR to remove the dead default constructor and get rid of the other commit --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[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_r67191945 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java --- @@ -0,0

[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_r67189534 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java --- @@ -0,0

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

Github user markap14 commented on a diff in the pull request: https://github.com/apache/nifi/pull/520#discussion_r67190819 --- Diff:

NIFI-2026: Opinion needed about adding non-Apache repos

All, Moving from GH as suggested by Matt. As part of NIFI-2026 I have been experimenting with ways of using non-vanilla Hadoop libraries when building NiFi from source. The idea is to streamline the overall process one must follow to get access to HDFS compatible platforms (e.g. MapR-FS)

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

Github user markap14 commented on the issue: https://github.com/apache/nifi/pull/520 @olegz I think github was having some problems the other day. I had 3 PR's that I created that did this, where it combined my branch from the previously submitted PR. #519 should not need to be here.

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

Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/520#discussion_r67190218 --- Diff:

[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_r67190110 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java --- @@ -0,0

[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_r67189259 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java --- @@ -0,0

[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_r67190072 --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java --- @@ -0,0

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

Github user markap14 commented on a diff in the pull request: https://github.com/apache/nifi/pull/520#discussion_r67190057 --- Diff:

Re: [DISCUSS] release line management

Tony, Joe, It sounds as though you would like to propose a change to this [1] release line management guidance that we generated as a result of the various discussions. Can you please propose some changes to that guidance? Of course, we must always work to support easy migration for

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

Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/475 The arg part is useful for more than just this case, perhaps it could be set to a more generic property such as "nifi.additional.java.args" or something, and done as a separate improvement.

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

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

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

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

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

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

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

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

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

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.

  1   2   >