[teiid-issues] [JBoss JIRA] (TEIID-5077) Couchbase strange behaviour for long numbers

[Steven Hawkins (JIRA)]

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

Steven Hawkins commented on TEIID-5077:
---------------------------------------

> Steven Hawkins What are the expectations for predefined DDL metadata by user? Should the property override the behaviour also in that case?

No, it would not fix this scenario.  Long is effectively a non-supported numeric source type, especially if you indicate useDouble.  So it is not expected that you would do this.  You can either accept precision limitation or use the string source type and a convert at the Teiid layer.  The issue with the latter approach is of course performance if you need to do any searching over the field as it will have to be done at the Teiid level.

> Couchbase strange behaviour for long numbers
> --------------------------------------------
>
>                 Key: TEIID-5077
>                 URL: https://issues.jboss.org/browse/TEIID-5077
>             Project: Teiid
>          Issue Type: Bug
>          Components: Documentation, Misc. Connectors
>    Affects Versions: 8.12.x-6.4
>            Reporter: Jan Stastny
>            Assignee: Steven Hawkins
>            Priority: Critical
>             Fix For: 10.0, 8.12.x-6.4, 9.3.4
>
>
> There is a strange limitation for storing large numbers (e.g. modelled as long) in Couchbase.
> https://forums.couchbase.com/t/strange-behavior-when-saving-big-long-numbers-3-0-1-ce/4793
> The same behaviour with value: 28341791043587382
> which is being stored and retreived as: 28341791043587384
> I feel we need to document this behaviour and provide hints how to overcome it. (Modelling of the column as string on Couchbase's side and defining a view).



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