[
https://issues.jboss.org/browse/TEIID-3061?page=com.atlassian.jira.plugin...
]
Ramesh Reddy resolved TEIID-3061.
---------------------------------
Labels: Alpha2 (was: )
Fix Version/s: 8.7.1
Resolution: Done
Added support for mapping BINARY data type of MongoDB to VARBINARY type in Teiid.
Previously it was read as object. If dynamic VDB with schema import was used it was mapped
to Blob. Now this will map to varbinary.
Caution needs to be taken by the user of this type to make sure the size does not exceed
8K per document, if it does then converting this data type to a Blob will resolve any
memory issues. That can be done by overriding the schema retrieved at deployment time and
defining the schema directly using DDL or using Teiid Designer.
However, if blob is used, if you write data though this translator then they will be
stored to GridFS. If needed, a enhancement can be added to store the Blob data as Binary
data.
See
https://docs.jboss.org/author/display/TEIID/Supported+Types
MongoDB: Support VARBINARY type
-------------------------------
Key: TEIID-3061
URL:
https://issues.jboss.org/browse/TEIID-3061
Project: Teiid
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Misc. Connectors
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Labels: Alpha2
Fix For: 8.7.1, 8.9
Map BinData structure of MongoDB to Teiid's VarBinary type, and MAP VARBINARY to
byte[]. Correct the import time byte[] to VARBINARY instead of blob.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)