Yep could do that too, the argument could just be something like:
java.arg.tmp=-Djava.io.tmpdir=/path/to/tmpdir
Regards,
Matt
On Fri, Jul 27, 2018 at 8:00 AM Otto Fowler wrote:
>
> Why not have the java tmp dir be configurable and make sure this doesn’t
> happen for any other possible nar?
>
This has been biting a few users lately, not sure when it changed
exactly, but the Hive NAR uses a version of Snappy that tries to
extract the native Snappy library into a location pointed to by the
"java.io.tmpdir" variable, which IIRC is /tmp/. The /tmp
directory sometimes has a noexec
Here is the error:
2018-07-26 18:48:49,013 ERROR [main] org.apache.nifi.NiFi Failure to launch
NiFi due to java.util.ServiceConfigurationError:
org.apache.nifi.processor.Processor: Provider
org.apache.nifi.processors.hive.PutHiveStreaming could not be instantiated
Geoff
Dont think it is a known issue. Many of us tested the
build/startup/etc.. Can you share the log output?
Thanks
On Thu, Jul 26, 2018 at 2:08 PM, geoff.craig wrote:
> Hello,
>
> I did a clean install of NiFi 1.7.1 and nifi-hive-nar-1.7.1.nar will not
> load. It throws a Ja
Geoff,
What error did you get? Please share it with us here.
On Thu, Jul 26, 2018 at 11:38 PM geoff.craig wrote:
> Hello,
>
> I did a clean install of NiFi 1.7.1 and nifi-hive-nar-1.7.1.nar will not
> load. It throws a Java error. I had to remove it from the folder to get
&g
Hello,
I did a clean install of NiFi 1.7.1 and nifi-hive-nar-1.7.1.nar will not
load. It throws a Java error. I had to remove it from the folder to get
NiFi running. Is this a known issue?
--
Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
