Mailing-List: contact commits-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@nifi.apache.org
Date: Thu, 1 Oct 2015 07:34:04 +0000 (UTC)
From: "Toivo Adams (JIRA)" <jira@apache.org>
To: commits@nifi.apache.org
Message-ID: <JIRA.12901644.1443634882000.129121.1443684844256@Atlassian.JIRA>
In-Reply-To: <JIRA.12901644.1443634882000@Atlassian.JIRA>
References: <JIRA.12901644.1443634882000@Atlassian.JIRA>
 <JIRA.12901644.1443634882824@arcas>
Subject: [jira] [Commented] (NIFI-1011) ExecuteSQL does not support Binary,
 VarBinary or LongVarBinary data types.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/NIFI-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939443#comment-14939443 ] 

Toivo Adams commented on NIFI-1011:
-----------------------------------

>From nifi-users mailing list 19 september

From
Mark Payne <marka...@hotmail.com>
Subject
Re: ExecuteSQL Processor / ArrayIndexOutOfBounds Exception
Date
Sat, 19 Sep 2015 00:23:28 GMT
Toivo,

I think for VARBINARY, LONGVARBINARY, ARRAY, BLOB, and CLOB, I would use an Avro Bytes type.


Basically, anything that could be serialized into a byte array i'd use a bytes type. Otherwise,
I'd probably just either fail or skip that column.
Not sure what else we can really do with this, at this point.

I have an instance of MySQL that I should be able to try this against at some point in the
next few days.

Thanks
-Mark


> On Sep 18, 2015, at 11:39 AM, Toivo Adams <toivo.adams@gmail.com> wrote:
> 
> Hi Jonathan,
> 
> It should not be tinyint, because such type is present in mapping code.
> I assume MySQL tinyint corresponds to JDBC java.sql.Types
>         public final static int TINYINT         =  -6;
> 
> I don't have MySQL so can't test directly.
> 
> Your table definition looks OK, nothing unusual and exotic.
> So hard to predict which type is culprit.
> 
> But ExecuteSQL needs some modifications anyway 
> because currently it does not recognize some rarely used types.
> 
> For example VARBINARY, LONGVARBINARY, OTHER, JAVA_OBJECT, ARRAY, BLOB, CLOB, etc.
> 
> How ExecuteSQL should handle type's which can't directly converted to Avro types?
> 
> 1. Always try to convert to String type? (we already convert some types to String)
> 2. Throw error?
> 3. what else...?


> ExecuteSQL does not support Binary, VarBinary or LongVarBinary data types.
> --------------------------------------------------------------------------
>
>                 Key: NIFI-1011
>                 URL: https://issues.apache.org/jira/browse/NIFI-1011
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 0.3.0
>         Environment: All
>            Reporter: Scott
>
> When trying to get a VarBinary or Binary column there is an ArrayIndexOutOfRangeException thrown. This is because in / nifi-nar-bundles / nifi-standard-bundle / nifi-standard-processors / src / main / java / org / apache / nifi / processors / standard / util / JdbcCommon.java the data types are not supported.
> I suggest adding them as Base64 encoded strings.


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