Hi Team,
We started using NIFI data flow in our current project by replacing node js
tcp listeners. we are using nifi listenTCP processor.
our use case: we have some devices they will send message to tcp port, from
nifi we have to get message and then place data into kafka.
Processors we are usi
Github user YolandaMDavis closed the pull request at:
https://github.com/apache/nifi/pull/424
---
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
Experts,
I have figured out how to CHANGE a flowfile's attributes (make a new one), but
not how to ADD to it new attributes. My tinkering is at this level currently:
**@Override
public void onTrigger(final ProcessContext context, final ProcessSession
session) throws ProcessException {
GitHub user alopresto opened a pull request:
https://github.com/apache/nifi/pull/508
NIFI-1981 Cluster communication without client certificate
This PR resolves an issue where cluster communications were failing when
the node sent a heartbeat without a client certificate chain becau
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/497
@markap14 I think I was able to reproduce the issue, it seems it happens
when theres more data in the queue than a RemoteProcessGroup can send at once.
I'll fix the issue.
---
If your project is
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/497
@markap14 I tested sending data using HTTP Site-to-Site with fresh build of
this PR. It successfully sent data. The exception happens when a client sends
data packet, but doesn't send additional d
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/477
They're evaluating RC3 as of this writing, I will be doing the same but I
expect good results and an imminent release :)
---
If your project is set up for it, you can reply to this email and have yo
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/497
@markap14 Thanks for taking time to try, and sorry to hear that it didn't
work. I'll check it. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user mans2singh commented on the issue:
https://github.com/apache/nifi/pull/239
@jvwing -
I've added displayName to PropertyDescriptor and updated name based on your
feedback.
I've not tried nifi on aws and mostly run it locally on my laptop that is
why I w
Github user noedetore commented on the issue:
https://github.com/apache/nifi/pull/477
Any update from ORC crew?
---
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
saikrishnat,
There are multiple processors that can get data from public web
services, such as InvokeHttp [1]. There are sample templates at [2],
including "Working_With_CSV.xml" which consumes a RESTful web service
at http://randomuser.me. If you are looking to discover/invoke
WSDL/SOAP services,
Hi ,
I am very new to NiFi. So far i can just move files between directories :).
I was trying access public web services like weather service by calling its
methods like getWeather,getCitiesByCountry etc..can i do that using NiFi and
how..? any help is much appreciated.
also any good resources for
Hey Oleg,
I would expect that we could match existing formatting and templates and
that Markdown files would result in more consistent html output than
everyone writing their own html by hand.
I agree though that we should make sure the look and feel can be made
consistent before moving forward.
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/498
---
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 enable
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/498
+1 This looks good, will merge to master and 0.x
---
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 featur
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/501
@YolandaMDavis I left several comments inline. Only other comment that I
have is that it feels a little weird to me to have `ControllerServiceLookup`
extend `VariableRegistryProvider`. These are reall
GitHub user bbende opened a pull request:
https://github.com/apache/nifi/pull/507
NIFI-1804 Adding ability for FileAuthorizer to automatically convert â¦
â¦existing authorized-users.xml to new model
You can merge this pull request into a Git repository by running:
$ git pull
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/501#discussion_r66148247
--- Diff: nifi-api/src/test/resources/TestVariableRegistry/test.properties
---
@@ -0,0 +1,2 @@
+fake.property.1=test me out 1
--- End diff --
Github user ckmcd closed the pull request at:
https://github.com/apache/nifi/pull/322
---
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 enabled
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/501#discussion_r66148213
--- Diff:
nifi-api/src/test/resources/TestVariableRegistry/foobar.properties ---
@@ -0,0 +1 @@
+fake.property.3=test me out 3, test me out 4
--- End di
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/501#discussion_r66148034
--- Diff:
nifi-api/src/test/java/org/apache/nifi/registry/TestVariableRegistry.java ---
@@ -0,0 +1,126 @@
+/*
+ * Licensed to the Apache Software Found
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/501#discussion_r66147759
--- Diff:
nifi-api/src/main/java/org/apache/nifi/registry/VariableRegistryUtils.java ---
@@ -0,0 +1,55 @@
+/*
+ * Licensed to the Apache Software Found
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/501#discussion_r66147340
--- Diff:
nifi-api/src/main/java/org/apache/nifi/registry/VariableRegistryUtils.java ---
@@ -0,0 +1,55 @@
+/*
+ * Licensed to the Apache Software Found
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/501#discussion_r66146877
--- Diff:
nifi-api/src/main/java/org/apache/nifi/registry/VariableRegistryFactory.java ---
@@ -0,0 +1,47 @@
+/*
+ * Licensed to the Apache Software Fou
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/501#discussion_r66146086
--- Diff:
nifi-api/src/main/java/org/apache/nifi/registry/VariableRegistry.java ---
@@ -0,0 +1,27 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/501#discussion_r66145978
--- Diff:
nifi-api/src/main/java/org/apache/nifi/registry/VariableRegistry.java ---
@@ -0,0 +1,27 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/501#discussion_r66145563
--- Diff: nifi-api/src/main/java/org/apache/nifi/registry/MultiMap.java ---
@@ -0,0 +1,154 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) u
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/501#discussion_r66145081
--- Diff: nifi-api/src/main/java/org/apache/nifi/registry/MultiMap.java ---
@@ -0,0 +1,154 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) u
Well that blows. Should I create a jira ticket to disable two phased
commit?
On Tuesday, June 7, 2016, Mark Payne wrote:
> Edgardo,
>
> You'd run into a lot of problems trying to use that solution, as many
> attributes contain
> characters that are not valid in HTTP headers, and HTTP Headers are
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/501#discussion_r66144229
--- Diff: nifi-api/src/main/java/org/apache/nifi/registry/MultiMap.java ---
@@ -0,0 +1,154 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) u
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/501#discussion_r66143984
--- Diff:
nifi-api/src/main/java/org/apache/nifi/registry/FileVariableRegistry.java ---
@@ -0,0 +1,70 @@
+/*
+ * Licensed to the Apache Software Founda
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/501#discussion_r66143013
--- Diff:
nifi-api/src/main/java/org/apache/nifi/registry/FileVariableRegistry.java ---
@@ -0,0 +1,70 @@
+/*
+ * Licensed to the Apache Software Founda
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/501#discussion_r66142811
--- Diff:
nifi-api/src/main/java/org/apache/nifi/registry/FileVariableRegistry.java ---
@@ -0,0 +1,70 @@
+/*
+ * Licensed to the Apache Software Founda
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/501#discussion_r66142774
--- Diff:
nifi-api/src/main/java/org/apache/nifi/registry/FileVariableRegistry.java ---
@@ -0,0 +1,70 @@
+/*
+ * Licensed to the Apache Software Founda
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/506
Hey @ckmcd I just realized that you had a different PR for the 0.x branch.
I ended up just creating a patch from PR 303 and applying that to the 0.x
baseline. So this should all be taken care of. Do y
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/303
@ckmcd looks good! I was able to test it locally. Unit tests are good. I
did find that a Reader was opened in a unit test and not closed, which i
addressed, and a couple of NOTICE files needed to be
Edgardo,
You'd run into a lot of problems trying to use that solution, as many
attributes contain
characters that are not valid in HTTP headers, and HTTP Headers are delineated
with
new-lines, so if you have an attribute with new-lines you'll get really weird
results.
-Mark
> On Jun 7, 2016,
Mark,
Amazon only supports sticky session via cookies.
Disabling the two-phase commit would be really nice
What if you do a invokehttp with send all the attributes as Http headers
and on the receive side on listenhttp do a .* to turn all the headers back
into attribute? Would that work?
Cheers,
The idea behind the DELETE mechanism is that in some environments there were
timeouts
that would occur quite frequently between PostHTTP / ListenHTTP and this
resulted in quite
a lot of data duplication. By adding in the two-phase commit, we were able to
drastically reduce
the amount of data dup
Personally I am ok either way, however the question I have is consistency and
how different artifacts written via html will be different (look-and-feel) from
the once created using mark up and then transformed.
Oleg
> On Jun 7, 2016, at 2:28 PM, Bryan Rosander wrote:
>
> Hey all,
>
> When w
Devs,
I see that the PutMongo processor's Collection property doesn't accept
expression language syntax. I've got JSON documents coming from multiple
sources (routed with an attribute I defined), and would like that attribute to
reflect which Mongo collection I insert into, which seems like th
Github user ckmcd commented on the issue:
https://github.com/apache/nifi/pull/303
This pull request should be good to go as all feedback has been
incorporated.
---
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 proj
Hey all,
When writing documentation (e.g. the additionalDetails.html for a
processor) it would be nice to have the option to use Markdown instead of
html.
I think Markdown is easier to read and write than raw HTML and for simple
cases does the job pretty well. It also has the advantage of being
GitHub user ckmcd opened a pull request:
https://github.com/apache/nifi/pull/506
NIFI-1660 - Enhance the expression language with jsonPath function
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ckmcd/nifi NIFI-1660-0.x
Alterna
InvokeHTTP may be the better option if the user is not interested in
transmitting content _packaged as_ FlowFiles. Someone with a bit more
history than myself can provide some additional context if I have strayed
off the path, but PostHTTP and ListenHTTP were precursors to Site to Site.
While they
Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/239
@mans2singh, the error messages did not contain anything helpful that
indicated it was a memory issue, just the text
`com.amazonaws.services.kinesis.producer.DaemonException: The child process has
been
Looks like PostHttp interprets the response, and based on a series of
conditions can intentionally issue a delete.
I can't fully understand what is happening, but the code is here:
https://github.com/apache/nifi/blob/1bd2cf0d09a7111bcecffd0f473aa71c25a69845/nifi-nar-bundles/nifi-standard-bundle/ni
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/505
+1 LGTM, tested it with and without command-line options, verified they are
passed to bower
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/505
---
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 enable
Joe,
We were testing with another nifi machine outside the elb to post a
flowfile in using the PostHttp processor. It seems that on each post there
is an immediate delete call. Behind the load balancer it goes haywire.
Cheers,,
Edgardo
On Tue, Jun 7, 2016 at 8:40 AM, Joe Witt wrote:
> Edgardo
GitHub user scottyaslan opened a pull request:
https://github.com/apache/nifi/pull/505
[NIFI-1707] create bower.options mvn property to support bower cli opâ¦
â¦tions...including --offline
You can merge this pull request into a Git repository by running:
$ git pull https://gi
Github user jfrazee closed the pull request at:
https://github.com/apache/nifi/pull/504
---
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 enabl
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/444
---
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 enable
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/497
@ijokarumawak I can't seem to get this to work properly. I configured nifi
to allow http site-to-site only, not secure. I then connected a
GenerateFlowFile processor to a Remote Process Group that poi
Github user brosander commented on the issue:
https://github.com/apache/nifi/pull/492
@mattyb149 I think I've addressed your suggestions, please let me know if
further changes are needed
---
If your project is set up for it, you can reply to this email and have your
reply appear on G
There was a whitespace issue in the test HL7 file. Joey moved the
content into the test class itself and removed the file. I reviewed
and merged to 0.x and master, so things should be back to normal.
Sorry for the hiccup.
Regards,
Matt
On Tue, Jun 7, 2016 at 10:03 AM, Matt Burgess wrote:
> I mer
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/504
+1 LGTM, tested on Apache and GitHub and tests are passing. Merging to 0.x
and master
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/504
Reviewing...
---
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 th
Github user jfrazee closed the pull request at:
https://github.com/apache/nifi/pull/495
---
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 enabl
GitHub user jfrazee opened a pull request:
https://github.com/apache/nifi/pull/504
NIFI-1979 Moved HL7 test file into TestExtractHL7Attributes to fix CRLF bug
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jfrazee/nifi NIFI-1979
Github user ijokarumawak commented on a diff in the pull request:
https://github.com/apache/nifi/pull/497#discussion_r66080066
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/api/SiteToSiteResource.java
---
@@
Github user ijokarumawak commented on a diff in the pull request:
https://github.com/apache/nifi/pull/497#discussion_r66078443
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-site-to-site/src/main/java/org/apache/nifi/remote/StandardRootGroupPort.java
---
@@ -
+ 1 on the build errors on HL7.
Seems to break things in here as well.
Cheers
On Tue, Jun 7, 2016 at 11:58 PM, Ryan H wrote:
> I did build the 0.x branch for the latest 0.7.0... It works when you skip
> building the tests.
>
I merged an HL7 PR last night, I will take a look. The tests passed
for me but maybe I screwed something up with the patch application.
On Tue, Jun 7, 2016 at 10:00 AM, Andre wrote:
> + 1 on the build errors on HL7.
>
> Seems to break things in here as well.
>
> Cheers
>
> On Tue, Jun 7, 2016 at
Here's a list of Jira cases in the NIFI project whose status is
Resolved and has an empty Fix Version:
https://issues.apache.org/jira/browse/NIFI-1892?jql=project%20%3D%20NIFI%20and%20status%20%3D%20Resolved%20and%20fixVersion%20is%20empty
On Tue, Jun 7, 2016 at 9:52 AM, Joe Witt wrote:
> Mike
>
I did build the 0.x branch for the latest 0.7.0... It works when you skip
building the tests.
The tests for nifi-hl7-processors aren't passing.
On Tue, Jun 7, 2016 at 9:52 AM, Joe Witt wrote:
> Mike
>
> Can you share a few pointers to ones you've noticed? Curious if there
> is a pattern.
>
> A
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/497
@mcgilman @markap14 I haven't touched RemoteProcessGroupAuditor.java with
this PR since I couldn't figure out the usage of this class. Processors shows
its audit in NiFi UI, but where can I see au
All,
I'm noticing a few JIRA tickets in the Resolved state, with commits against
them, but the Fix Version is none. I believe JIRA drives the release
notes, so we really should be diligent about making JIRA as accurate as
possible. I fix these tickets as I find them, but it would help if others
Mike
Can you share a few pointers to ones you've noticed? Curious if there
is a pattern.
As the community is growing we need to keep reviewing what to document
to help new people onboard but also to document things for those that
have been around for a while and just never knew to keep these thi
+1 for keeping JIRA accurate, I'll take a look too.
On Tue, Jun 7, 2016 at 9:48 AM, Michael Moser wrote:
> All,
>
> I'm noticing a few JIRA tickets in the Resolved state, with commits against
> them, but the Fix Version is none. I believe JIRA drives the release
> notes, so we really should be d
Github user ijokarumawak commented on a diff in the pull request:
https://github.com/apache/nifi/pull/497#discussion_r66071968
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/remote/StandardRemoteProcessGroup.java
---
That's awesome! Thanks Joe. We'll get 0.7.0 installed whenever it's cut
(RC or otherwise), and let you know if we see anything with it.
Ryan
On Tue, Jun 7, 2016 at 9:22 AM, Joe Witt wrote:
> Ryan
>
> I am supportive of that idea. I'll create an 0.7.1 version and move
> things over to it whic
Ryan
I am supportive of that idea. I'll create an 0.7.1 version and move
things over to it which seem feasible. Then send another note. If
folks need things shuffled we can address them.
Good call
Joe
On Tue, Jun 7, 2016 at 9:14 AM, Ryan H wrote:
> Any merit in cutting off the rest of the n
GitHub user ijokarumawak opened a pull request:
https://github.com/apache/nifi/pull/503
NIFI-1978: Restore RPG yield duration.
The persisted configuration value was not restored properly, and it will be
reset to default value 10 sec after restarting NiFi.
I found this issue
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/255#discussion_r66067616
--- Diff:
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/PutElasticsearch.java
-
Any merit in cutting off the rest of the non-critical issues, and planning
an 0.7.1 release? Not rush the dev, but cut something current for the rest
of us to start using and testing. Maybe even an RC?
On Tue, Jun 7, 2016 at 12:45 AM, Joe Witt wrote:
> NiFi 0.7.0 presently has 24 open tickets
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/248
I can continue the review on this one, mind rebasing against the latest
master or 0.x branch? Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Definitely agree with the spirit of this thread. I am happy to do a purge
on clearly dead branches.
Of note there was a decent chunk of time where we could create branches but
not remove them.
Thanks.
Joe
On Jun 7, 2016 8:25 AM, "Joe Skora" wrote:
> +1 for cleaning up the *Branches for resolve
Edgardo
Are you saying the clients are posting and then calling delete?
Also the more complex but flexible options are handle http request and
response.
Thanks
Joe
On Jun 7, 2016 7:04 AM, "Edgardo Vega" wrote:
> I wanted to throw Nifi behind a AWS ELB. I then have the ELB pointing at
> the nif
+1 for cleaning up the *Branches for resolved tickets* group.
The other groups should probably be reviewed by the last committers and
removed if appropriate.
A Jira ticket (or tickets) identifying each branch and its last commit hash
will document their removal while also making it easy to recrea
Devs,
It seems like the git tree is filled with stagnated / legacy branches
covering issues that have been already resolved.
Unclear ticket number
Branch name - last committer (date) - Suspected related issue
- improve-prov-performance - mcgilman (Apr 2015) - suspect it is NIFI-524
- journaling-p
I wanted to throw Nifi behind a AWS ELB. I then have the ELB pointing at
the nifi cluster. On the cluster I have a ListenHttp. I want to allow
people to post flow files to that url.
When testing this setup, it seems I am getting an error due to the fact it
seems like first there is a post and then
Github user mans2singh commented on the issue:
https://github.com/apache/nifi/pull/239
@jvwing -
Thanks again for your thorough review.
Just for my own learning, if there any pointers in the errors that
indicated it was a memory issue, please let me know. Also, is there any
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/257
@trixpan @olegz @michalklempa
I rebased the PR against master
---
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 doe
84 matches
Mail list logo
