Hey Martijn,
I had this exact issue once, and simply setting the catalog name fixed it for
me. Can you share (without the server names, of course) of a processor that
does this?
Also, are you running Nifi 1.7? This issue never happened to me in 1.5 but
happened in 1.7.
Thanks
-Alexandre
Apologies, I am talking about the DBCPCOnnectionPoolLookup. Long day...
On Thu, 25 Oct 2018, at 23:13, Martijn Dekkers wrote:
> Hello all,
>
> We ran into a weird issue. We use a DBCPConnectionPool to select the
> correct db for specific queries. Every so often (3 times now today,
> few times
Hello all,
We ran into a weird issue. We use a DBCPConnectionPool to select the
correct db for specific queries. Every so often (3 times now today, few
times yesterday) the DBCPConnectionPool will bug out with "Attributes
must contain an attribute name 'database.name'" event though the
Glad you were able to get it working.
Regarding the super user comment... I don't think it has to be a super
user, but it has to be a user that has permissions to perform the
action. For your example of "nifi pg-import" it would have to be a
user that has write permission to the parent process
@Juan, Thanks for the tip, probably not going to mount logs as using
Elastic filebeat to tail any live docker container logs - assuming that
nifi docker is configured to use the standard "docker log" API.
I've also found from experience that it is safer to move the default root
Docker volume
Hello,
Currently templates still have the issue mentioned in that JIRA, but
if you are trying to move flows between environments I would recommend
taking a look at NiFi Registry which will be much more powerful than
templates, and a versioned flow saved to registry will contain all of
the
Currently I don't think there is a way that config value can be set without
a code change, but if you want to create a JIRA it would probably make
sense to expose that as a property in the processor to toggle between true
and false, or we can also allow make it so that any dynamic properties get
If you want them to be on your host machine then you have to declare those
yes. By default docker will create directories for those volumes on the
docker host under /var/lib/docker/volumes/. Note: the docker host is
typically running in a VM, at least this is the case on Docker for Mac.
On Thu,
I suggest to be careful when mount log directory. In one day fills some
Gigabytes. If you want to mount logs, adjust the logging.
On Thu, 25 Oct 2018 at 10:07 Stephen Greszczyszyn
wrote:
>
>
> On Thu, 25 Oct 2018 at 12:50, Peter Wilcsinszky <
> peterwilcsins...@gmail.com> wrote:
>
> But even
On Thu, 25 Oct 2018 at 12:50, Peter Wilcsinszky
wrote:
But even with 1.8 I'll need to declare the host mount directory somehow via
docker-compose, as how will the built docker image on dockerhub know where
to locally mount the internal $(NIFI_HOME) volumes as described below?
VOLUME
On Thu, Oct 25, 2018 at 1:01 PM Stephen Greszczyszyn
wrote:
> Thanks for the reply Peter,
>
> You are right, last night when I tried mapping just /opt/nifi from NiFi
> version 1.7.1 the container wasn't happy starting up and I couldn't figure
> out what folders were needed to store state and
Thanks for the reply Peter,
You are right, last night when I tried mapping just /opt/nifi from NiFi
version 1.7.1 the container wasn't happy starting up and I couldn't figure
out what folders were needed to store state and manage any configurations.
Just to be clear, should I be mapping the
Hi Stephen,
I don't recommend mounting /opt/nifi directly as it will copy all the NiFi
binaries over to the volume as well, which is unnecessary I beleive. The
latest dockerfile that will be used to build the docker image for the
upcoming release already declares volumes that I recommend to
Hi All,
Currently in one of my Nifi instance flow is having DistributedMapCacheServer
controller service and wanted to run same flow in another instance. I tried
saving and loading template but DistributedMapCacheServer controller is not
saved in template.
1. I see JIRA issue
Hi,
We have an issue with PutParquet (NiFi 1.7.1), well with the parquet lib to
be precise, and array type data containing null values.
This is a schema snippet of the field in question:
{
"name": "adresse",
"type" : ["null", { "type" : "array", "items" :
15 matches
Mail list logo
