You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Burgess (JIRA)" <ji...@apache.org> on 2018/09/04 13:23:02 UTC

[jira] [Resolved] (NIFI-5563) SQL processors may generate Avro-incompatible column names

     [ https://issues.apache.org/jira/browse/NIFI-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Burgess resolved NIFI-5563.
--------------------------------
    Resolution: Not A Bug

I verified in code that this is not a bug, the names are correctly handled by JdbcCommon and ExecuteSQL. There is an issue with generated schemas not producing Avro-compatible names, but that should be covered by NIFI-5552 and its associated PR. Closing this as not a bug.

> SQL processors may generate Avro-incompatible column names
> ----------------------------------------------------------
>
>                 Key: NIFI-5563
>                 URL: https://issues.apache.org/jira/browse/NIFI-5563
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Matt Burgess
>            Priority: Major
>
> Although the "Convert Names for Avro" property in such processors as ExecuteSQL replaces non-Avro characters with underscores, it doesn't validate/alter the names to ensure they are Avro compatible. For example, SELECT 1 may give a column name of 1, but Avro names have to start with one of [A-Za-z_]. We need to check for that and prefix an underscore if the name doesn't start with one of those characters. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)