All,
As I have been working around restricting the level of filesystem
privileges required by NiFi to run, I started to wonder how to tackle what
in my opinion is one of the biggest challenges around NiFi:
How to ensure the ExecuteProcessors, FS processors (GetFile/PutFile) aren't
misused by a
Russ,
As Jeff points out lack of available threads could be a factor flow
slower processing times but this would manifest itself by you seeing
that the processor isn't running very often. If it is that the
process itself when executing takes much longer than on the other box
then it is probably
I am trying to run a remote script through a script in my host environment
from the ExecuteProcess processor in NiFi. Basically, the shell script in
the host server has the ssh string to the remote server and calling the
script in that remote server. I used sshpass package where I saved the
I compile trough Maven on intellij 2016 but the problem comes from antlr
v3. A language parser that is not understood natively by the compiler. I
tried the antlworks plugin but It still didn't. I'll try tomorow read the
doc to configure it properly
Le 3 oct. 2016 17:22, "Mark Payne"
Russel,
This sounds like it's an environmental issue. Are you able to see the heap
usage on the production machine? Are there enough available threads to get
the throughput you are observing when you run locally? Have you
double-checked the scheduling tab on the processor config to make sure
Mathias,
How are you trying to compile it? If using Maven, it should work just fine. If
you are using
an IDE such as Eclipse you may need to first compile via Maven to get the
generated code
and then add those directories as source directories.
Thanks
-Mark
> On Oct 3, 2016, at 10:33 AM,
I am reviewing the PR for NIFI-2774 ConsumeJMS and we need someone to
review the PR for NIFI-2429 PersistentProvenanceRepository. Once those are
complete I think we can start the process to cut 0.7.1.
-- Mike
On Mon, Oct 3, 2016 at 9:49 AM, Tony Kurc wrote:
> So, sounds like
Hi All,
I have an issue trying to compiling project nifi-hl7-query-language due to
HL7Query.java file
Compiler doesn't found depdency
import org.apache.nifi.hl7.query.antlr.HL7QueryLexer;
import org.apache.nifi.hl7.query.antlr.HL7QueryParser;
I see the files HL7QueryLexer.g and
So, sounds like we have enough support to go ahead. How are we feeling
about what our timeline should be on this?
On Wed, Sep 28, 2016 at 11:14 PM, Joe Witt wrote:
> +1 to an 0.7.1 with the bugs that have been addressed already.
> Even bigger +1 to Tony volunteering as RM!
We use NiFi for an ETL feed. On one of the lines, we use a custom
processor, *VelocityTemplating* (calls Apache Velocity), which work very
well and indeed is imperceptibly fast when run locally on the same data
(template, VTL macros, substitution fodder). However, in production it's
another
10 matches
Mail list logo