[teiid-issues] [JBoss JIRA] (TEIID-5027) Translator infinispan-hotrod incorrect data type import

[Ramesh Reddy (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453643#comment-13453643 ] 

Ramesh Reddy commented on TEIID-5027:
-------------------------------------

[~jstastny] Thinking more about it, the issue is more about not preserving the data types when DDL form is presented in the source model than data types itself. When this is preserved, then the conversion from long to data/time will happen at translation layer without any "convert" operations. 

> Translator infinispan-hotrod incorrect data type import
> -------------------------------------------------------
>
>                 Key: TEIID-5027
>                 URL: https://issues.jboss.org/browse/TEIID-5027
>             Project: Teiid
>          Issue Type: Bug
>          Components: JDG Connector, Misc. Connectors
>    Affects Versions: 8.12.x-6.4
>            Reporter: Jan Stastny
>            Assignee: Steven Hawkins
>            Priority: Blocker
>
> I have a vdb:
> {code:xml|title=jdg71_crud-vdb.xml}
> <vdb name="jdg71_crud" version="1">
>     <model name="Source" type="PHYSICAL" visible="true">
>         <source name="jdg7-source" translator-name="infinispan-hotrod" connection-jndi-name="java:/jdg71HotrodDS" />
>         <metadata type="DDL"><![CDATA[
>              CREATE FOREIGN TABLE SmallA (
>                IntKey integer,
>                IntNum integer,
>                DoubleNum double,
>                ObjectValue object,
>                BigDecimalValue bigdecimal,
>                BigIntegerValue biginteger,
>                CharValue char,
>                StringNum string,
>                StringKey string PRIMARY KEY,
>                FloatNum float,
>                LongNum long,
>                TimeValue time,
>                ShortValue short,
>                ByteNum byte,
>                TimeStampValue timestamp,
>                BooleanValue boolean,
>                DateValue date) OPTIONS(UPDATABLE true, "teiid_ispn:cache" '${jdg.cache.name}');
>             ]]>
>         </metadata>
>         <metadata type = "NATIVE"/>
>     </model>
> </vdb>
> {code}
> But the resulting metadata are:
> || column_name | column_type ||
> || IntKey | integer ||
> || IntNum | integer ||
> || DoubleNum | double ||
> || ObjectValue | string ||
> || BigDecimalValue | varbinary ||
> || BigIntegerValue | varbinary ||
> || CharValue | string ||
> || StringNum | string ||
> || StringKey | string ||
> || FloatNum | float ||
> || LongNum | long ||
> || TimeValue | varbinary ||
> || ShortValue | integer ||
> || ByteNum | integer ||
> || TimeStampValue | varbinary ||
> || BooleanValue | boolean ||
> || DateValue | varbinary ||
> All the columns should be replaced by appropriate data type as defined in the vdb.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)