[
https://issues.jboss.org/browse/TEIID-2329?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2329:
-------------------------------------
Commited initial version of MongoDB support to github master.
This feature adds the support to integrate MongoDB as one of the supported sources in the
Teiid. This commit consists of a connector module and translator module. The translator
DOES NOT have capability to provide metadata to Teiid based on already existing MongoDB.
The user is expected to define a schema that they want to use with MongoDB. This is
designed explicitly keeping in mind of good segment of users that want move their data
from RDBMS to MongoDB, or starting out with MongoDB, but know their schema and prefer to
work with SQL and not get tangled with MongoDB specific dialect. The choice of MongoDB may
be for scaling and performance.
This translator can convert SELECT, INSERT, UPDATE and DELETE calls appropriately the
MongoDB specific dialect. There are extended metadata features available, that can let
users build a single complex document in MongoDB based on multiple individual tables in
the VDB Schema defined for MongoDB. Supports creation of indexes on MongoDB. Supports
aggregation and functions exposed by the MongoDB. This translator uses MongoDB
"aggregation" framework for all the queries, so selecting the MongoDB version
that has support for "aggregation" framework is mandatory. I developed using
MongoDB 2.4.1
Currently I have not added support for LOBs and Composite Keys and native queries. These
are still pending, depending upon on time scale for 8.4 either get implemented or pushed
to next version. Documentation will be added
Add support for Mongo DB as a data source
-----------------------------------------
Key: TEIID-2329
URL:
https://issues.jboss.org/browse/TEIID-2329
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Ramesh Reddy
Fix For: 8.4, Open To Community
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira