[
https://issues.apache.org/jira/browse/NIFI-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471333#comment-15471333
]
ASF GitHub Bot commented on NIFI-2262:
--------------------------------------
GitHub user mattyb149 opened a pull request:
https://github.com/apache/nifi/pull/994
NIFI-2262: Added Avro-normalization of table/column names in SQL processors
Affected processors are QueryDatabaseTable and ExecuteSQL, since they
generate Avro output. GenerateTableFetch is not affected as it generates SQL,
however I added the property to the AbstractDatabaseFetchProcessor class so it
could be reused by future processors.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mattyb149/nifi NIFI-2262
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/994.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #994
----
commit f452d36d076200084cf0c8823979a948a070adc2
Author: Matt Burgess <[email protected]>
Date: 2016-09-07T17:53:47Z
NIFI-2262: Added Avro-normalization of table/column names in SQL processors
----
> SQL processors fail if column name contains characters illegal for Avro
> -----------------------------------------------------------------------
>
> Key: NIFI-2262
> URL: https://issues.apache.org/jira/browse/NIFI-2262
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Matt Burgess
> Assignee: Matt Burgess
>
> For SQL processors that output Avro (ExecuteSQL, QueryDatabaseTable, etc.),
> if the SQL result set contains columns whose names contain Avro-illegal
> characters (such as a period), then an error occurs:
> org.apache.avro.SchemaParseException: Illegal character in: user.gender
> These processors should either normalize the names for Avro automatically or
> have a property indicating whether names should be normalized.
> A workaround for ExecuteSQL in many cases is to alias the columns in the SQL.
> This approach doesn't currently work in QueryDatabaseTable for incremental
> fetch (i.e. maximum-value columns)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
