Mark
Thanks for trying. Indeed I forgot to mention in the guide that one has to add
‘nifi.properties.file.path' as ‘VM Arguments’, updating the guide now.
As for logging, everything should work. Even though NiFi uses logback adapter
for slf4j, the IDE setup uses log4j and all required JARs
Also, validate that src/main/resources is one of the source directories, so
log4j.properties is pulled into the startup class path. I was just able to
reproduce your exact error by disassociating it from the class path.
On Oct 27, 2015, at 6:51 AM, Oleg Zhurakousky
Mark,
I don't think there is a strong preference for patches vs. pull requests. A
lot of contributors use pull requests, and I personally find it easier to
review pull requests because you can give feedback in-line on the code. The
more important thing is that whatever is being submitted should
Hey Cathy,
There are many processors that cover pushing/pulling from databases as well as
doing some transformations. You can check out the list here:
https://nifi.apache.org/docs.html
Let us know if you need more help,
Joe
- - - - - -
Joseph Percivall
linkedin.com/in/Percivall
e:
It appears you’ve misconfigured your Run Configuration.
It seems like your MainClass is org.apache.nifi.bootstrap.RunNifi. It should be
org.apache.nifi.NiFi
Can you verify?
Oleg
> On Oct 27, 2015, at 8:45 AM, Mark Petronic wrote:
>
> On Tue, Oct 27, 2015 at 6:55 AM,
Mark
The following output comes from RunNifi which starts org.apache.nifi.NiFi as a
separate JVM process which means you are not really in full DEBUG mode anyway:
opt/java/jdk1.7.0_75/bin/java
-Dnifi.properties.file.path=/home/mpetronic/nifi-0.3.1-SNAPSHOT/./conf/nifi.properties
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/108
NIFI-1074 added initial support for IDE integration
Includes instructions for Eclipse
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/olegz/nifi
On Tue, Oct 27, 2015 at 6:55 AM, Oleg Zhurakousky
wrote:
> I was just able to reproduce your exact error by disassociating it from the
> class path
Oleg, thanks for the response.
1. I verified that my working directory is correct and points to my
running version