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

Github user jvwing commented on the pull request: https://github.com/apache/nifi/pull/239#issuecomment-222062467 Is `REL_FAILURE` used in GetKinesis? --- 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 1540 - AWS Kinesis Get and Put Processors

Github user jvwing commented on the pull request: https://github.com/apache/nifi/pull/239#issuecomment-222057686 Your suggestion about the plain old SDK Kinesis API is interesting, but I guess I don't recommend it. Using the plain SDK would let NiFi handle the multithreading,

Re: Best way to process the processor requests in batch

Kumiko A couple of quick thoughts to share. You can absolutely code your processor to operate in batches and you can of course multi-thread the processor. The general unit of work concept Apache NiFi supports is called a ProcessSession and you can operate on as many flow files as you need in

[GitHub] nifi pull request: NIFI-1815

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

[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#issuecomment-222020291 Hi @jvwing - Thanks for your feedback. Regarding changing the hierarchy to create a `AmazonWebServiceClient` independent base class - I can create

[GitHub] nifi pull request: NIFI-1564: No supported viewer issue

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/421 --- 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: NIFI-1554: Updating Cluster endpoints

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/470 --- 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: NIFI-1554: Updating Cluster endpoints

Github user markap14 commented on the pull request: https://github.com/apache/nifi/pull/470#issuecomment-221954497 +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

[GitHub] nifi-minifi pull request: MINIFI-30 added changes to the config tr...

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi-minifi/pull/17#discussion_r64796094 --- Diff: minifi-bootstrap/src/main/java/org/apache/nifi/minifi/bootstrap/util/ConfigTransformer.java --- @@ -616,15 +630,21 @@ private static void

[GitHub] nifi pull request: NIFI-1800: Providing access to Controller Servi...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/469 --- 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: NIFI-1800: Providing access to Controller Servi...

Github user markap14 commented on the pull request: https://github.com/apache/nifi/pull/469#issuecomment-221951022 +1 looks good to me. --- 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

Re: site to site communication error on output port

Ok great, I see some data Bryan, the problem is because my Spark application had some classnotfound exceptions on nifi jars, but still started somehow on some executors, had to see the yarn log to see what those are, and the reason I started that path was because I could not see the streaming tab

Re: [discuss] Proposed addition of replaceRegex to expression language

Got it. That makes sense and provides all the variations of functionality so it sounds like a win! On Thu, May 26, 2016 at 1:21 PM, Andy LoPresto wrote: > Hi Joe, > > I think what you proposed is more than is necessary. replaceAll is > functionally complete already, as if

[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_r64785162 --- Diff: nifi-nar-bundles/nifi-ocr-bundle/nifi-ocr-processors/src/main/java/org/apache/nifi/processors/ocr/TesseractOCRProcessor.java --- @@ -0,0 +1,361 @@

Re: [discuss] Proposed addition of replaceRegex to expression language

Hi Joe, I think what you proposed is more than is necessary. replaceAll is functionally complete already, as if it is passed a literal expression, it will compile it as such and replace all instances in the subject string. I think the confusing point is that the difference between replace and

[GitHub] nifi pull request: NIFI-1668 modified TestProcessorLifecycle to en...

Github user olegz commented on the pull request: https://github.com/apache/nifi/pull/324#issuecomment-221935626 @markap14 the "idempotency" comment is valid and I agree for that alone we don't need multiple threads. I'll look again to see if test name matches with what I was actually

[GitHub] nifi pull request: NIFI-1668 modified TestProcessorLifecycle to en...

Github user markap14 commented on the pull request: https://github.com/apache/nifi/pull/324#issuecomment-221935156 Agreed - I think moving the FlowController lifecycle to @Before and @After should address the issues. I do think that the validateIdempotencyOfProcessorStartOperation()

[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_r64783794 --- Diff: nifi-nar-bundles/nifi-ocr-bundle/nifi-ocr-processors/src/main/java/org/apache/nifi/processors/ocr/TesseractOCRProcessor.java --- @@ -0,0 +1,361 @@

[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_r64783731 --- Diff: nifi-nar-bundles/nifi-ocr-bundle/nifi-ocr-processors/src/main/java/org/apache/nifi/processors/ocr/TesseractOCRProcessor.java --- @@ -0,0 +1,361 @@

[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_r64783373 --- Diff: nifi-nar-bundles/nifi-ocr-bundle/nifi-ocr-processors/src/main/java/org/apache/nifi/processors/ocr/TesseractOCRProcessor.java --- @@ -0,0 +1,361 @@

Re: [discuss] Proposed addition of replaceRegex to expression language

I think there is transitional path that is non-breaking and could prevent 0.x to 1.x migration issues, even if at the expense of a little extra code for a period of time. 1. Leave the existing "replace" and "replaceAll" functions as is for now. 2. Implement the new "replaceRegex" and

[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_r64782839 --- Diff: nifi-nar-bundles/nifi-ocr-bundle/nifi-ocr-processors/src/main/java/org/apache/nifi/processors/ocr/TesseractOCRProcessor.java --- @@ -0,0 +1,361 @@

[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_r64782640 --- Diff: nifi-nar-bundles/nifi-ocr-bundle/nifi-ocr-processors/src/main/java/org/apache/nifi/processors/ocr/TesseractOCRProcessor.java --- @@ -0,0 +1,361 @@

[GitHub] nifi pull request: NIFI-1554: Updating Cluster endpoints

GitHub user mcgilman opened a pull request: https://github.com/apache/nifi/pull/470 NIFI-1554: Updating Cluster endpoints - Refactoring Cluster endpoints. - Updating frontend to accommodate clustering endpoints. - Remove the 'Make Primary' action. This is phase one

[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_r64781939 --- Diff: nifi-nar-bundles/nifi-ocr-bundle/nifi-ocr-processors/src/main/java/org/apache/nifi/processors/ocr/TesseractOCRProcessor.java --- @@ -0,0 +1,361 @@

[GitHub] nifi pull request: NIFI-1815

Github user olegz commented on the pull request: https://github.com/apache/nifi/pull/397#issuecomment-221929351 Ok, so I'll start reviewing this, but wanted to mention that at the current state there are merge conflicts so feel free to fix them whenever or let me know and I can help.

[GitHub] nifi pull request: NIFI-1668 modified TestProcessorLifecycle to en...

Github user olegz commented on the pull request: https://github.com/apache/nifi/pull/324#issuecomment-221925828 "...how come the that issue wouldn't cause all following tests to fail..." some times it does. You may want to consult with Mark on that since that error originates from

[GitHub] nifi pull request: NIFI-1668 modified TestProcessorLifecycle to en...

Github user olegz commented on the pull request: https://github.com/apache/nifi/pull/324#issuecomment-221917899 The issue is not with before, but with _after_, since it effectively acts as a _finally_ block. The way it was before if a test failed for whatever reason, then the

[GitHub] nifi pull request: NIFI-1668 modified TestProcessorLifecycle to en...

Github user JPercivall commented on the pull request: https://github.com/apache/nifi/pull/324#issuecomment-221903401 Also I might be alone here, but I dislike the unit tests that create an executor to run something many times sometime in the future and then waiting to see if it will

[GitHub] nifi pull request: NIFI-1668 modified TestProcessorLifecycle to en...

Github user JPercivall commented on the pull request: https://github.com/apache/nifi/pull/324#issuecomment-221901178 How will moving the building of the flow controller to the before method help the OverlappingFileLockException? The before and after methods are run immediately before

[GitHub] nifi pull request: NIFI-1800: Providing access to Controller Servi...

GitHub user mcgilman opened a pull request: https://github.com/apache/nifi/pull/469 NIFI-1800: Providing access to Controller Services based on a given context - UI style updates to make the components stand out better. - Reusing controller service table in different contexts

Re: site to site communication error on output port

You should only need one of the FetchFile processors, otherwise you are fetching every file twice. If you start that flow so everything is green, and then run your spark job, do you still get the error? On Thu, May 26, 2016 at 9:36 AM, pradeepbill wrote: > Please find

[GitHub] nifi pull request: NIFI-1925: Fixed typo in error message

Github user jdye64 commented on the pull request: https://github.com/apache/nifi/pull/468#issuecomment-221889685 Nice catch Simon. Little things like that are hard to find. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

Re: site to site communication error on output port

Please find my new flow. nifi1.PNG -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/site-to-site-communication-error-on-output-port-tp10698p10727.html Sent from the Apache NiFi

Re: site to site communication error on output port

Thanks Bryan, Yes , I do not need a RPG, I will try with the approach you mentioned and will get back to you. Thanks Pradeep Sent from my iPhone > On May 26, 2016, at 6:24 AM, Bryan Bende [via Apache NiFi Developer List] > wrote: > > Hi Pradeep, > >

Re: site to site communication error on output port

Hi Pradeep, Thanks for sending the information about your flow. From looking at the picture, I'm not sure I fully understand what the flow is doing... It looks like there is a GetFile processor connected to a Remote Process Group (RPG) which goes to an Input Port called app_logs, and I see the

[GitHub] nifi-minifi pull request: MINIFI-30 added changes to the config tr...

Github user apiri commented on a diff in the pull request: https://github.com/apache/nifi-minifi/pull/17#discussion_r64732477 --- Diff: minifi-bootstrap/src/main/java/org/apache/nifi/minifi/bootstrap/util/ConfigTransformer.java --- @@ -616,15 +630,21 @@ private static void

Re: [DISCUSS] Apache NiFi 0.7.0 and 1.0.0

Ok just to wrap up this thread. Will push a couple efforts 1) Will start pulling together an 0.7 release 2) Will update the roadmap slide to put in tentative timing/major elements in the roadmap on the wiki page And as for whether 0.7 ends up being the last release of the 0.x line will just

Re: Apache NiFi 0.7.0 Release date ?

Hello Ved We were recently talking about doing the 0.7.0 release timed similarly with the 1.0.0 release. But that might be too long of a wait and the 0.7 line has plenty of good things in it. What in particular are you looking for from it? Also, your emails do get through but they require

Apache NiFi 0.7.0 Release date ?

Hi , When is NiFi 0.7.0 release planned? PS: i am not sure whether my posts and mails are reaching to you guys. My sincere apology if this question has been repeated. Regards, -Ved -- View this message in context:

[GitHub] nifi pull request: NIFI-1925: Fixed typo in error message

GitHub user simonellistonball opened a pull request: https://github.com/apache/nifi/pull/468 NIFI-1925: Fixed typo in error message You can merge this pull request into a Git repository by running: $ git pull https://github.com/simonellistonball/nifi NIFI-1925 Alternatively

Re: Apache NiFi expression language

Andy, as always thank you for your reply (and apologies for delay of my response too). Just to clarify, I have come across this issue while using the processor ReplaceTextWithMapping. I shared a related post with the community: