Hi Vikram,
The current site-to-site protocol is part of the core NiFi framework and is not
extendible without modifying the NiFi source code to replace/add a custom
protocol where the existing protocol is implemented. Can you describe the
problem you are hoping to solve? Perhaps someone on
Hi,
I see that the Site-2-Site data transfer supports both RAW and Http
protocols. Is it possible to extend this to support custom protocols?
Regards,
Vikram
All,
I've just released version 1.2.0 of the nifi-script-tester [1], a
utility that lets you test your Groovy, Jython, and Javascript scripts
for use in the NiFi ExecuteScript processor. Here are the new
features:
- Upgraded code to NiFi 1.4.0
- Added support for incoming flow file attributes
I haven't done anything like this before? how do I implement this in nifi
On Thu, Oct 5, 2017 at 3:08 PM, Matt Burgess wrote:
> Austin,
>
> There is an open Jira (NIFI-2278 [1]) to add this support to the
> existing processor(s), I believe if Apache Commons Net is used for
Just to follow up on Matt’s comments, the *name* value is used when the flow is
serialized to the flow.xml.gz file and deserialized. For example, if a property
descriptor has name “ssl-protocol-version” and value “SSL 3.0”, the XML would
look like:
Something using SSLSSL 3.0
…
Now, when
Austin,
There is an open Jira (NIFI-2278 [1]) to add this support to the
existing processor(s), I believe if Apache Commons Net is used for the
clients then we would just need to create an FTPSClient [2] instead of
an FTPClient. In order to support prototyping such things, Apache
Commons Net was
Giovanni,
For the session.each(), a rollback will occur if an exception is not
caught. ExecuteScript catches anything bad that happens from the
script itself, and will perform the rollback. If you catch your own
exceptions, you have much more control over how the flow files (and
the overall
Hi,
Has anyone tried integrating MSMQ with Apache NiFi (sender/receiver)? Is it
even possible?
As per MS documentation – “Message Queuing applications can be developed using
C++ APIs or COM objects. Applications can be built in any of the popular
development environments: for example,
Has anyone successfully implemented a flow that can perform an ftps (ftp
with tls/ssl) there is not a standard option for this. We can successfully
wget the data but are having trouble ftping in general. any advice?
--
Austin Duncan
*Researcher*
PYA Analytics
2220 Sutherland Avenue
I did some more testing and found that if I restart the NiFi instance that is
running the reporting task, I start getting provenance events again in my other
instance.
If I stop the reporting task, add the DOWNLOAD filter, restart the task and
then generate only download events, those download
I had a SiteToSiteProvenanceReportingTask running in 1.3.0, so I gave this a
try myself.
I think I’m able to reproduce the issue that Fred is seeing. But I’m not sure
if the issue is only related to adding an Event Type filter to the reporting
task.
With no filter, I generated some DOWNLOAD
Hi Fred,
I have used the reporting task with specific event types listed, but I've not
run into issues personally.
I am curious if you have tried looking for more common event types, such as
RECEIVE, CONTENT_MODIFIED, or ATTRIBUTES_MODIFIED?
EXPIRE events only fire when FlowFiles get aged off
Hi Vikram,
This is not currently possible. There has been some initial work and some
discussion on C2 capabilities that are in progress of being designed/built
out [1][2]. There is heartbeating and providing operations for an agent to
carry out that has an initial implementation in C++. There
Hi,
Is it possible to monitor and manage the MiniFi agents that connect to
NiFi server from a the NiFi Server UI?
Regards,
Vikram
14 matches
Mail list logo