Bug 888935 - Create a MongoDB connector for EDS - Feature Request
Summary: Create a MongoDB connector for EDS - Feature Request
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER2
: 6.0
Assignee: Van Halbert
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-19 20:02 UTC by Joel Tosi
Modified: 2016-10-05 23:06 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-03-10 20:45:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-2329 0 Major Closed Add support for Mongo DB as a data source 2014-03-10 20:45:04 UTC

Description Joel Tosi 2012-12-19 20:02:51 UTC
Description of problem:
There isn't a connector for MongoDB

Version-Release number of selected component (if applicable):


How reproducible:
Eh, try to use a MongoDB connector, see one doesn't exist

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 JBoss JIRA Server 2013-03-07 23:50:30 UTC
Steven Hawkins <shawkins> made a comment on jira TEIID-2329

Pulling into 8.4 for further evaluation.

Comment 2 JBoss JIRA Server 2013-04-24 21:25:23 UTC
Ramesh Reddy <rareddy> updated the status of jira TEIID-2329 to Coding In Progress

Comment 3 JBoss JIRA Server 2013-05-21 16:44:45 UTC
Ramesh Reddy <rareddy> made a comment on jira 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

Comment 4 JBoss JIRA Server 2013-06-04 17:47:08 UTC
Ramesh Reddy <rareddy> updated the status of jira TEIID-2329 to Resolved

Comment 5 JBoss JIRA Server 2013-06-04 17:47:08 UTC
Ramesh Reddy <rareddy> made a comment on jira TEIID-2329

Added support for LOBs, and created JIRAs for enhancements 
- Composite PKs
- native query
- should add one supporting array type based any requests

Comment 12 belong 2013-11-19 23:24:40 UTC
Fixed before GA - setting to requires_doc_text- accordingly

Comment 13 JBoss JIRA Server 2013-12-05 20:51:40 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-2329 to Closed

Comment 14 Filip Nguyen 2014-02-17 17:30:52 UTC
will be tested as a post GA activity


Note You need to log in before you can comment on or make changes to this bug.