Hi Karthikeyan,
Thanks for your response. It works fine for me..
Regards,
Ravi
On Tue, May 3, 2016 at 3:31 AM, karthi keyan
wrote:
> Ravisankar
>
> Did you passed the "Processor Entity as json" in the the Body(
> application/json).
>
> Since its optional entity in
Just to provide an update. I did rewrite the same logic in lua and used in
executescript processor. The performance is 5-10x faster compare to jython.
very pleased with performance of lua processor.
Next steps:
will checkout https://issues.apache.org/jira/browse/NIFI-1822 to test multiple
As some of you know, we are in the process of providing a set of new Processors
that uses the new Kafka API (0.9+). This is a new NAR and will live for a while
along side with the old Kafka NAR.
The new Processors are called PublishKafka and ConsumeKafka (specifically to
emphasize the new
Totally makes sense. My only comment was just in regards to the fact that
on that Wiki page there is no mention of looking at GH PR's. I agree that
in this day and age looking to GH, may be first inclination for many.
However, perhaps calling that out in the contribution guide would eliminate
The "Patch Available" state in JIRA can mean a patch is attached to the
JIRA, or a PR is submitted.
It is really just a manual state transition on the ticket after
In-Progress... the next state is patch available which tells people there
is something to review.
On Tue, May 3, 2016 at 11:29 AM,
They are treated with same priority, but as Oleg mentioned, the PRs do make
it easier for collaborative review and has the built in integration with
Travis, although currently some issues to get it consistently working.
On Tue, May 3, 2016 at 11:26 AM, Suneel Marthi wrote:
>
Totally agree on all fronts. Would seem like it makes sense for a
documentation PR to be opened soon with updates to the
https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide#ContributorGuide-CodeReviewProcess
page to remove the ambiguity.
On Tue, May 3, 2016 at 11:27 AM, Bryan
Andrew
Regarding PR vs. Patch.
This has been an ongoing discussion and i’ll let other’s to contribute to this.
Basically we support both. That said, personally (and it appears to be embraced
by the rest of the community) PR is the preference specifically due to the
inline review/comment
Oleg,
I would love to help -- couple of quick questions:
The GH PR's are ~60 as you indicated, but the How To Contribute guide (Code
review process --
https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide#ContributorGuide-CodeReviewProcess
) shows a JIRA list with patches available.
Guys
I’d like to use this opportunity to address all members of the NiFi community
hence this email is sent to both mailing lists (dev/users)
While somewhat skeptical when I started 6 month ago, I have to admit that now I
am very excited to observe the growth and adaption of the Apache NiFi
I am also running on windows and for status and stop script, I just created a
copy of run file and changed the BOOTSTRAP_ACTION in it. It works fine.
Regards,
Manish
From: Tom Jerry [mailto:toejam20...@gmail.com]
Sent: Tuesday, May 03, 2016 7:25 PM
To: users@nifi.apache.org
Subject: Re: NiFi
Thanks for the reply.
There also used to be a run-nifi.bat and stop-nifi.bat scripts, but they
are no longer in /bin
The two files are still listed in the Admin Guide.
No worries - quite a lot of functions to understand fully. That's why we have
the community! :)
Cheers
-Mark
> On May 3, 2016, at 8:28 AM, Devin Fisher
> wrote:
>
> Yes, that is perfect. I guess I did not read them all carefully enough.
> Thanks.
>
>
Yes, that is perfect. I guess I did not read them all carefully enough.
Thanks.
Devin
On Tue, May 3, 2016 at 1:22 PM, Mark Payne wrote:
> Hi Devin,
>
> I think the 'replaceNull' function is what you are looking for. For
> example:
>
> ${
Hi Devin,
I think the 'replaceNull' function is what you are looking for. For example:
${ greeting:replaceNull('hello'):length():gt(5) }
You can find the documentation for this function at
http://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#replacenull
What is the guidance regarding the best way to run Apache NiFi on
Windows. Pre-Apache release used to have installation scripts for
installing NiFi as a service. Now that the wrapper stuff has been
removed, what is recommended?
-Tom
Ravisankar
Did you passed the "Processor Entity as json" in the the Body(
application/json).
Since its optional entity in what scenario it expecting the XY coordinates
?
Then try with sample json to parse the configurations for the Processor.
Thanks,
Karthikeyan
On Tue, May 3, 2016 at 12:07
Hi All,
I have tried to access the NiFi processor using Rest Api
Reference
https://nifi.apache.org/docs/nifi-docs/rest-api/
In this case, i need to use already created template, so i will try the
following API
Syntax:
POST
/controller/process-groups/{process-group-id}/processors
Creates a
18 matches
Mail list logo