I'm using Apache Nifi 1.9.2 and trying to post JSON content to a
BigQuery table.
There seems to be something wrong, sicne I get
2019-07-03 08:35:24,964 ERROR [Timer-Driven Process Thread-8]
o.a.n.p.gcp.bigquery.PutBigQueryBatch
PutBigQueryBatch[id=b2b1c6bf-016b-1000-e8c9-b3f9fb5b417e]
Hi Nicolas,
It seems that NiFi expects to have the "mode" field being present, even
though based on the BigQuery doc [1] it's optional.
I'd suggest trying adding it to every name-type pair with its default value
"NULLABLE". (i.e. { "name": "Consent", "type": "record", *"mode":
"NULLABLE"*,
I'm ivnestigating the same way.
I've added the mode field everywhere, but still have the issue.
I'll try to create a minimal reproducing schema for your ticket (by
running unit tests)
Le 03/07/2019 à 11:28, Denes Arvay a écrit :
Hi Nicolas,
It seems that NiFi expects to have the "mode"
Hi,
I've read on Docker hub that nifi docker container doesn't support
OpenID Connect.
But if I mount the nifi.properties file using a volume, is it possible
to have openID Connect working ? or is it replaced by the Docker
start.sh script (which invoke secure.sh only for LDAP or two-way SSL) ?
So I have a simple test that replicate the bug. Do I have to open the
issue in Apache JIRA (I already have access to) ?
Le 03/07/2019 à 11:28, Denes Arvay a écrit :
Hi Nicolas,
It seems that NiFi expects to have the "mode" field being present,
even though based on the BigQuery doc [1] it's
Well, if you take a look at my schema, the error is subtle, but obvious
(once I've added the tests and modified the code).
I've set "Consent" to be of typ "record", not "RECORD". Yes, it was a
case issue.
So I've modified code in BigQueryUtils to use uppercased type in all
cases, AND an
Yes, and please attach the test cases too.
Does this mean that your original issue hasn't been resolved yet by adding
the "mode" fields?
On Wed, Jul 3, 2019, 19:27 Nicolas Delsaux wrote:
> So I have a simple test that replicate the bug. Do I have to open the
> issue in Apache JIRA (I already
I believe the wording on the Docker Hub page simply means the environment
variables are not mapped for OpenID Connect configuration through Docker. If
you mount a pre-configured NiFi.properties file with OpenID Connect provider
configured, I am not aware of any reason that would not work as
