[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=13453101#comment-13453101 ] 

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

ProtoBuf protocol on which this transalator is based on supports limited data types which can be seen at [1], if you are defining anything other than these then they will be by default byte[] or varbinary.

There may be an enhancement we can do preserve the data types at Teiid layer, but it is not without hurdles. The best thing we can do for now is to KI the issue that some of the data types in Teiid like (biginteger, bigdecimal, timestamp, etc) will not be supported natively in Infinispan, the user needs to create a separate view and convert them to respective type.

So basically when you define DDL in Infinispan source model, use only types supported by protobuf, if needs more types then create a view on it.

[1] https://developers.google.com/protocol-buffers/docs/proto3#scalar

> 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 VIEW 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)