[
https://issues.jboss.org/browse/TEIID-5077?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5077:
---------------------------------------
Modelling of the column as string on Couchbase's side and
defining a view
I don't see from that posting that the Couchbase client is to blame, but potentially
other JSON parsers - has it been confirmed that this directly affects our Couchbase usage.
Also does the proposed workaround actually work? If the view contains a conversion to
biginteger/long, that would currently be pushed to couchbase as the to_number function and
if there is an issue with the json serialization/deserialization in the Couchbase client,
you'd seemingly still hit the issue.
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
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-numb...
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)