nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Toivo Adams (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (NIFI-972) ExecuteSQL bug in createSchema() create Arvo Schema method
Date Thu, 01 Oct 2015 14:40:28 GMT

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

Toivo Adams updated NIFI-972:
-----------------------------
    Attachment: nifi-972_01oct2015.patch

BINARY, VARBINARY, LONGVARBINARY, ARRAY, BLOB, CLOB are now supported.
ARRAY is not tested, others tested lightly using H2 database.
Other databases may have slightly different behavior.


> ExecuteSQL bug in createSchema() create Arvo Schema method
> ----------------------------------------------------------
>
>                 Key: NIFI-972
>                 URL: https://issues.apache.org/jira/browse/NIFI-972
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Toivo Adams
>         Attachments: nifi-972_01oct2015.patch
>
>
> Jonathan Lyons reported:
> Just getting started with NiFi here. I am attempting to run a static query
> in MySQL using the ExecuteSQL processor. It is set to run on a 5 second
> interval. Since ExecuteSQL appears to need an input flow file I'm using a
> GenerateFlowFile processor to produce a random file every 5 seconds.
> Unfortunately, I'm getting a very vague ArrayIndexOutOfBounds exception
> when I hit play on the flow:
> java.lang.ArrayIndexOutOfBoundsException: 8
> at org.apache.avro.generic.GenericData$Record.put(GenericData.java:129)
> at org.apache.nifi.processors.standard.util.JdbcCommon.convertToAvroStream
> at
> org.apache.nifi.processors.standard.ExecuteSQL$1.process(ExecuteSQL.java:141)
> It’s seem to be bug in createSchema() which creates Arvo schema.
> When createSchema() will encounter unknown type, no Arvo column info will be created.
And Arvo schema has less columns than ResultSet row…



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message