Github user trixpan commented on the pull request:
https://github.com/apache/nifi/pull/179#issuecomment-173830226
@bbende I have been running some tests that I usually use around reliable
destinations (disconnects, repeated messages, unexpected restarts) and all
worked to expected (ex
Github user sejasp commented on the pull request:
https://github.com/apache/nifi/pull/180#issuecomment-173806065
PostHTTP has been working like a charm. However, GetElasticsearch would be
a great addition to the "Get" processors. Preferably, scrolling.
---
If your project is set up
Github user trkurc commented on the pull request:
https://github.com/apache/nifi/pull/167#issuecomment-173795089
Not sure that I agree, but I do agree this is a step in the right
direction, so I'll merge it in.
---
If your project is set up for it, you can reply to this email and hav
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/167
---
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 trixpan commented on the pull request:
https://github.com/apache/nifi/pull/180#issuecomment-173770694
sounds like a great idea
---
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
Github user trkurc commented on the pull request:
https://github.com/apache/nifi/pull/179#issuecomment-173770289
@bbende - this is an awesome contribution. most of my comments are minor
and of the ilk of we should fix next chance we get, with the exception of the
'comand' typo
Github user mattyb149 commented on the pull request:
https://github.com/apache/nifi/pull/180#issuecomment-173769666
You are right that more processing would be needed to coax the flow file
into the right format for the *Http processors. If the ES processors were to
use the HTTP API th
Github user trkurc commented on a diff in the pull request:
https://github.com/apache/nifi/pull/179#discussion_r50490991
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ListenRELP.java
---
@@ -0,0 +1,224 @@
Github user trkurc commented on a diff in the pull request:
https://github.com/apache/nifi/pull/179#discussion_r50490685
--- Diff:
nifi-commons/nifi-processor-utilities/src/main/java/org/apache/nifi/processor/util/listen/dispatcher/SocketChannelDispatcher.java
---
@@ -0,0 +1,243 @
Paresh,
Also wanted to let you know another upcoming feature is our multi-tenant
data flow [1]. One of the concepts being considered is creating separate
workspaces. This would essentially offer multiple root level Process Groups
that could provide different levels of authorization. This could
pot
Github user trkurc commented on a diff in the pull request:
https://github.com/apache/nifi/pull/179#discussion_r50490353
--- Diff:
nifi-commons/nifi-processor-utilities/src/main/java/org/apache/nifi/processor/util/listen/dispatcher/DatagramChannelDispatcher.java
---
@@ -0,0 +1,164
Github user trkurc commented on a diff in the pull request:
https://github.com/apache/nifi/pull/179#discussion_r50490153
--- Diff:
nifi-commons/nifi-processor-utilities/src/main/java/org/apache/nifi/processor/util/listen/dispatcher/DatagramChannelDispatcher.java
---
@@ -0,0 +1,164
Github user trkurc commented on a diff in the pull request:
https://github.com/apache/nifi/pull/179#discussion_r50490135
--- Diff:
nifi-commons/nifi-processor-utilities/src/main/java/org/apache/nifi/processor/util/listen/dispatcher/DatagramChannelDispatcher.java
---
@@ -0,0 +1,164
Github user trkurc commented on a diff in the pull request:
https://github.com/apache/nifi/pull/179#discussion_r50489858
--- Diff:
nifi-commons/nifi-processor-utilities/src/main/java/org/apache/nifi/processor/util/listen/dispatcher/ChannelDispatcher.java
---
@@ -0,0 +1,39 @@
+
Paresh,
Input/Output ports are allowed to be inside of Process Groups. These
facilitate data flow in between the Process Group and it's parent Process
Group. In the case of the root Process Group, it facilitates remote data
flows with other NiFi instances (or anything that can speak the
site-to-si
Github user trkurc commented on a diff in the pull request:
https://github.com/apache/nifi/pull/179#discussion_r50489401
--- Diff:
nifi-commons/nifi-processor-utilities/src/main/java/org/apache/nifi/processor/util/listen/AbstractListenEventProcessor.java
---
@@ -0,0 +1,356 @@
Github user trixpan commented on the pull request:
https://github.com/apache/nifi/pull/180#issuecomment-173761891
@mattyb149 very good point... very good point
Indeed and according to a blog post on found.no(Elastic's cloud offering)
back in January suggested the use of transp
In our use case to keep the UI managable we create different ProcessorGroups
for the different pipelines. But when using the RemoteProcessorGroups and
InputPorts we are forced to move the pipelines out of the processor groups and
into the root canvas. This helps us tear down and do the deploymen
GitHub user PuspenduBanerjee opened a pull request:
https://github.com/apache/nifi/pull/186
Nifi-Camel Integration Initial Commit
It's initial working version of nifi-camel integration.
As per feature request NIFI-924
You can merge this pull request into a Git repository by run
GitHub user mattyb149 opened a pull request:
https://github.com/apache/nifi/pull/185
NIFI-210: Add ExecuteScript and InvokeScriptProcessor
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mattyb149/nifi script-processors
Alternat
Github user mattyb149 commented on the pull request:
https://github.com/apache/nifi/pull/180#issuecomment-173740429
Yes this controller is using the Transport protocol. The explicit docs you
mention are logstash docs, not elasticsearch docs. The Elasticsearch Java
Client docs
(https:
Github user trixpan commented on the pull request:
https://github.com/apache/nifi/pull/180#issuecomment-173737898
Is it my impression or this controller is embedding elastic search into
NiFi in order to use the Transport protocol?
Would this cause all sort of issues around ver
GitHub user rpmiskin opened a pull request:
https://github.com/apache/nifi/pull/184
NIFI-1421 Update SplitXML to support namespace declarations
I've done a fairly minimal update to SplitXML to correctly support
namespace declarations.
Let me know if I've missed anything.
Y
Github user bbende commented on the pull request:
https://github.com/apache/nifi/pull/179#issuecomment-173726265
Thanks for reviewing @mcgilman and @trkurc !
I pushed up a small commit that fixed a couple of minor logging issues and
addressed the comment Matt made about the p
Github user trkurc commented on the pull request:
https://github.com/apache/nifi/pull/179#issuecomment-173712640
@mcgilman - I have been reviewing. I should be complete tonight. Haven't
found any show stoppers yet.
---
If your project is set up for it, you can reply to this email and
GitHub user ledor473 opened a pull request:
https://github.com/apache/nifi/pull/183
NIFI-1423 Allow to penalize FlowFiles to No Retry
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ledor473/nifi penalize-http-no-retry
Alternati
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/179#issuecomment-173707708
Spent some time reviewing the patch. Overall, I think the code looks good.
Additional nit-picky item outside of my previous comment.
- I could see possibly wantin
Github user mattyb149 closed the pull request at:
https://github.com/apache/nifi/pull/144
---
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 ena
GitHub user mattyb149 opened a pull request:
https://github.com/apache/nifi/pull/182
NIFI-1412: Fix error during Avro conversion where no fields are present
Changes the logic so no exception is thrown when meta.getColumnCount()
returns 0, instead an empty Avro schema is produced.
Y
That long thread has no attached images since LifeLock seems unable to
receive them.
On Thu, Jan 21, 2016 at 2:48 PM, Joe Witt wrote:
> not to take away from the thread but Matt I didn't get your images either
>
> On Thu, Jan 21, 2016 at 2:45 PM, Matthew Clarke
> wrote:
> > Paresh,
> >
> >
For Site-to-Site to work between NiFi instances, the following need to be
in place:
1. Firewalls have to be open to allow all source nodes to talk to all
destination nodes through the Site-To-Site port configured in the target
nodes nifi.properties file.
2. Firewalls have to be open to allow all s
not to take away from the thread but Matt I didn't get your images either
On Thu, Jan 21, 2016 at 2:45 PM, Matthew Clarke
wrote:
> Paresh,
>
> I am really not sure why you are not getting by attachments. Other
> are receiving them fine. Is it possible the LifeLock email servers are
> dropp
Paresh,
I am really not sure why you are not getting by attachments. Other
are receiving them fine. Is it possible the LifeLock email servers are
dropping them?
I think we need to take one step back and talk a little more about
what input and output ports are used for.
Lets st
Github user mcgilman commented on a diff in the pull request:
https://github.com/apache/nifi/pull/179#discussion_r50451076
--- Diff:
nifi-commons/nifi-processor-utilities/src/main/java/org/apache/nifi/processor/util/listen/dispatcher/DatagramChannelDispatcher.java
---
@@ -0,0 +1,1
Github user markobean commented on a diff in the pull request:
https://github.com/apache/nifi/pull/135#discussion_r50449323
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/SplitText.java
---
@@ -198,23 +208
ok great -thanks
On Thu, Jan 21, 2016 at 2:21 PM, Paresh Shah wrote:
> I did not see the option to pick the port when dragging the RPG. This is
> no longer a problem.
>
>
> On 1/21/16, 10:10 AM, "Paresh Shah" wrote:
>
>>To clarify I do see the ports in the RPG but am not able to turn them
>>“On”
I did not see the option to pick the port when dragging the RPG. This is
no longer a problem.
On 1/21/16, 10:10 AM, "Paresh Shah" wrote:
>To clarify I do see the ports in the RPG but am not able to turn them
>“On”. That option is only available for the first in the list.
>
>Paresh
>
>On 1/21/16
To clarify I do see the ports in the RPG but am not able to turn them
“On”. That option is only available for the first in the list.
Paresh
On 1/21/16, 9:55 AM, "Paresh Shah" wrote:
>I¹m not sure where I would see the ports being called remote group ports.
>Using the UI I picked the Input Port
I¹m not sure where I would see the ports being called remote group ports.
Using the UI I picked the Input Port on to the canvas at the root level
and am able to see one of them successfully in the RemoteProcessorGroup.
Also I do not see any place where I can set the authorization level.
On 1/21/
Paresh,
Screenshots through the apache mailing lists require pretty specific
delivery mechanism which honestly I don't know. So...best to find a
way to link to screenshots or to put them in a JIRA.
When you create InputPorts at the root group level they become
available as ports that another aut
I have created different set of InputPorts for the different pipelines. But
when I see the list of InputPorts in the RPG I do not see option to pick other
ports except the first one in the list.
I have attached the screeshots
The information contained in this t
When the RemoteProcessorGroup has been EnabledForTransmission, the exception
seen in the log file is
2016-01-21 09:01:05,477 WARN [NiFi Site-to-Site Connection Pool Maintenance]
o.a.n.r.c.socket.EndpointConnectionPool EndpointConnectionPool[Cluster
URL=http://localhost:9080/nifi] Unable to ref
GitHub user thadguidry opened a pull request:
https://github.com/apache/nifi/pull/181
Give extra info about input dir for Windows users.
Windows users typically don't have to worry about supplying a trailing
slashuntil they work with some Java programs like Nifi.
An input pa
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/167#issuecomment-173604806
@trkurc I do see your point, so let me throw something else at you. The
_URI_VALIDATOR_ simply validates based on success of this ```new URI(input);```
and we can certainly
Yashwant
Thank you for your interest in Apache NiFi. From the questions you
have at this stage it sounds like you are in the very early stages of
learning about NiFi. Please take a look at the following starting
points:
NiFi Website [1]
NiFi Documentation [2]
NiFi Videos/Talks [3]
[1] https://
Hi Team,
I am Yashwant Chandrakar currently working at Brillio as big data consultant.
I am looking forward to use apache nifi to understand the data flow purpose.
Could you please help me out to understand the following below points regards
with nifi.
1. How I can use the nifi to unde
46 matches
Mail list logo
