You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Marcio Sugar (JIRA)" <ji...@apache.org> on 2019/01/23 18:43:00 UTC
[jira] [Created] (NIFI-5971) ExecuteSQL Avro schema: all fields are
nullable
Marcio Sugar created NIFI-5971:
----------------------------------
Summary: ExecuteSQL Avro schema: all fields are nullable
Key: NIFI-5971
URL: https://issues.apache.org/jira/browse/NIFI-5971
Project: Apache NiFi
Issue Type: Improvement
Components: Extensions
Affects Versions: 1.7.1
Environment: Ubuntu 16.04
Apache NiFi 1.7.1
IBM DB2 for Linux, UNIX and Windows 10.5.0.7, 10.5.0.8
IBM Data Server Driver for JDBC and SQLJ, JDBC 4.0 Driver (db2jcc4.jar) 4.19.26 / v10.5 FP6, 4.19.72 / v10.5 FP9
Reporter: Marcio Sugar
JdbcCommon#createSchema creates an Avro schema with nullable types for all fields. It should check with java.sql.ResultSetMetaData#isNullable instead.
It's the same issue discussed on dev list [here|https://lists.apache.org/list.html?dev@nifi.apache.org:2018-12] a few months ago. A workaround exists, but it's inconvenient when you have lots of tables to deal with. I like the solution proposed by Matt Burgess, the "Honor Non-Nullable Fields" property.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)