[GitHub] nifi pull request: NIFI-1754 Rollback log messages should include the flowfi...

Github user trkurc commented on a diff in the pull request: https://github.com/apache/nifi/pull/478#discussion_r65299383 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/repository/StandardProcessSession.java

[GitHub] nifi pull request: NIFI-856 Implements experimental ListenLumberjack Process...

Github user trixpan commented on a diff in the pull request: https://github.com/apache/nifi/pull/290#discussion_r65298978 --- Diff: nifi-nar-bundles/nifi-lumberjack-bundle/nifi-lumberjack-processors/src/main/java/org/apache/nifi/processors/lumberjack/ListenLumberjack.java --- @@

[GitHub] nifi pull request: NIFI-856 Implements experimental ListenLumberjack Process...

Github user apiri commented on a diff in the pull request: https://github.com/apache/nifi/pull/290#discussion_r65298320 --- Diff: nifi-nar-bundles/nifi-lumberjack-bundle/nifi-lumberjack-processors/src/main/java/org/apache/nifi/processors/lumberjack/ListenLumberjack.java --- @@

[GitHub] nifi pull request: NIFI-856 Implements experimental ListenLumberjack Process...

Github user trixpan commented on a diff in the pull request: https://github.com/apache/nifi/pull/290#discussion_r65297806 --- Diff: nifi-nar-bundles/nifi-lumberjack-bundle/nifi-lumberjack-processors/src/main/java/org/apache/nifi/processors/lumberjack/ListenLumberjack.java --- @@

Re: [DISCUSS] Apache NiFi 0.7.0 and 1.0.0

I'll take release manager duties for 0.7.0 unless someone else with committer status really wants to give it a go. Right now there are 43 tickets assigned to it. I'll go through and punt ones on there that seem stalled or deferrable. Of course, if there are any that are particularly important

Re: [DISCUSS] Apache NiFi 0.7.0 and 1.0.0

Also looking forward to using the TransformJSON processor: https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/TransformJSON.java Nice choice with JOLT there. We're doing a custom one for jolt

[GitHub] nifi pull request: NIFI-1916 Updating FileAuthorizer to extend AbstractPolic...

Github user mcgilman commented on the pull request: https://github.com/apache/nifi/pull/473 @bbende Just realized that we'll need to introduce some thread safety here. The RevisionManager in the web tier will handle locking during the User/Group/Policy CRUD operations. However,

[GitHub] nifi pull request: NIFI-1916 Updating FileAuthorizer to extend AbstractPolic...

Github user jtstorck commented on a diff in the pull request: https://github.com/apache/nifi/pull/473#discussion_r65270822 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-file-authorizer/src/main/java/org/apache/nifi/authorization/FileAuthorizer.java --- @@

[GitHub] nifi pull request: NIFI-1916 Updating FileAuthorizer to extend AbstractPolic...

Github user jtstorck commented on a diff in the pull request: https://github.com/apache/nifi/pull/473#discussion_r65268067 --- Diff: nifi-api/src/main/java/org/apache/nifi/authorization/AccessPolicy.java --- @@ -28,15 +28,15 @@ private final String identifier;

Re: Nifi Java 1.7 support

Sounds great.  Thanks.  Mans On Tuesday, May 31, 2016 1:56 PM, Joe Witt wrote: We are moving to Java 8 minimum with the 1.0 release of nifi.  Looks like maybe July as a release timing.  We will still support 0.x for some aspects and for some time which is java 7

[GitHub] nifi pull request: NIFI-1815

Github user rkarthik29 commented on a diff in the pull request: https://github.com/apache/nifi/pull/397#discussion_r65261047 --- Diff: nifi-nar-bundles/nifi-ocr-bundle/nifi-ocr-processors/src/main/java/org/apache/nifi/processors/ocr/TesseractOCRProcessor.java --- @@ -0,0 +1,359

Re: Nifi Java 1.7 support

Yes, that would be with NIFI 1.0.0 Cheers Oleg > On May 31, 2016, at 4:51 PM, M Singh wrote: > > Hi Folks: > > Just wanted to find out if there is a timeline when Nifi will sunset support > for JDK 1.7. > Thanks > Mans

Nifi Java 1.7 support

Hi Folks: Just wanted to find out if there is a timeline when Nifi will sunset support for JDK 1.7. Thanks Mans

[GitHub] nifi pull request: Nifi 1540 - AWS Kinesis Get and Put Processors

Github user mans2singh commented on the pull request: https://github.com/apache/nifi/pull/239 Hey Folks: For this pull request - Travis-ci build is passing for me but appveyor is failing in the nifi-framework-core module with the following error. Please let me know if there is

RE: DistributedMapCacheServer

Thanks Bryan. I will try it and let you know. Thanks again for your help. Shishir -Original Message- From: Bryan Bende [mailto:bbe...@gmail.com] Sent: Tuesday, May 31, 2016 3:44 PM To: dev@nifi.apache.org Subject: Re: DistributedMapCacheServer Hello, Not totally sure if this will work

[GitHub] nifi pull request: NIFI-1815

Github user rkarthik29 commented on a diff in the pull request: https://github.com/apache/nifi/pull/397#discussion_r65249839 --- Diff: nifi-nar-bundles/nifi-ocr-bundle/nifi-ocr-processors/src/main/java/org/apache/nifi/processors/ocr/TesseractOCRProcessor.java --- @@ -0,0 +1,359

Re: DistributedMapCacheServer

Hello, Not totally sure if this will work for every case, but at some point in your flow you could split off and send a flow file to ReplaceText, and set the Replacement Value to ${your.attribute} to overwrite the content of that flow file with your attribute value, from there send to

[GitHub] nifi pull request: NIFI-1815

Github user olegz commented on the pull request: https://github.com/apache/nifi/pull/397 @jdye64 I had a chance to play with it today. Looking good and is simple enough (which I like, since it leaves enough room for new features/improvements as we learn usage patterns). Left a

[GitHub] nifi pull request: NIFI-1815

Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/397#discussion_r65247766 --- Diff: nifi-nar-bundles/nifi-ocr-bundle/nifi-ocr-processors/src/main/java/org/apache/nifi/processors/ocr/TesseractOCRProcessor.java --- @@ -0,0 +1,359 @@

[GitHub] nifi pull request: NIFI-1815

Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/397#discussion_r65247502 --- Diff: nifi-nar-bundles/nifi-ocr-bundle/nifi-ocr-processors/src/main/java/org/apache/nifi/processors/ocr/TesseractOCRProcessor.java --- @@ -0,0 +1,359 @@

Re: How to unsubscribe from this alias

Hi Dan, I think you should have received a mail with a link to confirm you want to unsubscribe the mailing list. Pierre 2016-05-31 21:08 GMT+02:00 Dan S : > I tried sending unsubscribe emails to > > >1. users-unsubscr...@nifi.apache.org >2.

DistributedMapCacheServer

Hi, I have a use case where I am looking to store only one attribute from my flowfile to DistributedMapCacheServer. My flowfile is potentially large so I am not looking to push complete flowfile to DistributedMapCacheServer. At a quick glance, it looks like I can store complete flowfile

How to unsubscribe from this alias

I tried sending unsubscribe emails to 1. users-unsubscr...@nifi.apache.org 2. dev-unsubscr...@nifi.apache.org 3. commits-unsubscr...@nifi.apache.org yet I am still getting email from dev@nifi.apache.org How can I unsubscribe successfully?

Jetty request filtering of NiFI API requests

I have a legacy system that makes requests against the NiFi API, but some requests don't come in quite right. In lieu of changing the legacy system, it would be great if I can create a Jetty request filter that 1) corrects the URL path and 2) changes or removes some header values. First, can

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

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

[GitHub] nifi pull request: NIFI-1919 Add replaceFirst method to expression language

Github user alopresto commented on the pull request: https://github.com/apache/nifi/pull/474 Fixed the re-organization of import sections by the IDE. --- 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: NIFI-1829 - Create new DebugFlow processor.

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

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

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

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

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

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

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

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

Github user trkurc commented on the pull request: https://github.com/apache/nifi/pull/458 reviewing this --- 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,

Re: back pressure

Also, just wanted to clarify... I didn't mean to make it sound like back-pressure can't help with external sources, it really depends on the processor and protocol being used. I was thinking mostly of ListenSyslog with UDP, and since UDP is connectionless back-pressure can't really help here.

[GitHub] nifi pull request: NIFI-1754 Rollback log messages should include the flowfi...

Github user trkurc commented on a diff in the pull request: https://github.com/apache/nifi/pull/478#discussion_r65223758 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/repository/StandardProcessSession.java

[GitHub] nifi pull request: NIFI-1754 Rollback log messages should include the flowfi...

Github user trkurc commented on a diff in the pull request: https://github.com/apache/nifi/pull/478#discussion_r65219394 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/repository/StandardProcessSession.java

Re: back pressure

Your scenario brings up an interesting point... back-pressure can only help you with in NiFi, meaning that in a push scenario, NiFi has no way of telling the syslog server (or any external source) to stop sending messages. The way the syslog processor works, there is a background thread receiving

Re: back pressure

Hi Pradeep, Back-pressure tells the source component to no longer execute when the threshold has been reached. For example, say you have a GetFile -> PutHDFS and you configure and object threshold of 100 on the queue between them. If the queue gets to 100, GetFile will no longer be allowed to

back pressure

hi there, I am trying to understand what the below text says from NIFI documentation, 1. What does back pressure mean really in NIFI?, here is my simple flow, Some NIFI-source -> Some NIFI processor. If the amount of input data from the source is more than the amount of data the processor can

[GitHub] nifi pull request: NIFI-1754 Rollback log messages should include the flowfi...

Github user trkurc commented on a diff in the pull request: https://github.com/apache/nifi/pull/478#discussion_r65196703 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/repository/StandardProcessSession.java

[GitHub] nifi pull request: NiFi 1945 - Corrects minor issue in "

GitHub user trixpan opened a pull request: https://github.com/apache/nifi/pull/481 NiFi 1945 - Corrects minor issue in "" description Fixes typo identified in NIFI-1945 You can merge this pull request into a Git repository by running: $ git pull https://github.com/trixpan/nifi

[GitHub] nifi pull request: NIFI-1754 Rollback log messages should include the flowfi...

Github user trkurc commented on the pull request: https://github.com/apache/nifi/pull/478 I've started reviewing this one --- 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

[GitHub] nifi pull request: NIFI-1943 added proper ReadsAttribute to PutFile

GitHub user JPercivall opened a pull request: https://github.com/apache/nifi/pull/480 NIFI-1943 added proper ReadsAttribute to PutFile You can merge this pull request into a Git repository by running: $ git pull https://github.com/JPercivall/nifi NIFI-1943 Alternatively you

[GitHub] nifi pull request: NIFI-1937 GetHTTP configurable redirect cookie policy

GitHub user mosermw opened a pull request: https://github.com/apache/nifi/pull/479 NIFI-1937 GetHTTP configurable redirect cookie policy NIFI-1937 allows GetHTTP to configure a cookie policy in Apache HTTPClient to use for redirects. You can merge this pull request into a Git

[GitHub] nifi pull request: Nifi 1540 - AWS Kinesis Get and Put Processors

Github user mans2singh commented on the pull request: https://github.com/apache/nifi/pull/239 Hi @jvwing - I made the changes you had recommended (added unit tests for get and put kinesis, renamed the get and put processors, added comments about usage of DynamoDB and Cloud Watch),