er 16, 2022 10:59 AM
> To: users@nifi.apache.org
> Subject: [EXTERNAL] Re: json into a json-enabled DB
>
> EXT email: be mindful of links/attachments.
>
>
>
> To Matt's point, I've tested insert by doing a record field of String going
> to JSON/JSONB in Postgres and MySQL, a
ecember 16, 2022 10:59 AM
To: users@nifi.apache.org
Subject: [EXTERNAL] Re: json into a json-enabled DB
EXT email: be mindful of links/attachments.
To Matt's point, I've tested insert by doing a record field of String going to
JSON/JSONB in Postgres and MySQL, and that worked just fine.
I'
To Matt's point, I've tested insert by doing a record field of String
going to JSON/JSONB in Postgres and MySQL, and that worked just fine.
I'm not sure if we're at a point where we can do a reader with one
schema and a writer with another schema, but it should be pretty
straight forward to fix so
Geoffrey,
The biggest problem with JSON columns across the board is that the
JDBC and java.sql.Types specs don't handle them natively, and NiFi
records don't recognize JSON as a particular type, we are only
interested in the overall datatype such as String since NiFi records
can be in any
Some databases (postgres, sql server, others) support native json columns.
With postgres, there's a native jsonb type, with sql server it's a string type,
that you can treat as json.
In any event, once you have the json in the database, one can then query it,
e.g.:
SELECT id,product_name,
