[
https://issues.jboss.org/browse/TEIIDDES-1981?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIIDDES-1981:
----------------------------------------
-1, for adding the BIRT releated connecton profile. I suggest, you to remove it. We got be
pushing all the connection profiles towards the DS based, that is only way we can get out
this connection profile confusions. A BIRT based connection profile only *required* when
designer is using it to import the data, which it is not. Otherwise the DS based should be
used always.
Some basic metadata importing has been added to MongoDB translator in 8.7. It may not work
with complex documents but simple documents should work. See
https://issues.jboss.org/browse/TEIID-2849
IMO, the way Teiid Connection importer should work is, when the importer does not return
any tables it should still go ahead and create a "empty" source model but finish
creating the data source stuff etc. Such that when user does add a view manually it works
seamlessly. Or give a user an option to create a empty model rather than terminating the
whole process. That way JBoss DS is always created when Teiid Connection Importing is
used.
The same goes for any source that is explicitly using "Teiid Connection
Importer" for importing metadata. We got to clean those verbose connection profiles
up.
MongoDB issues in Designer
--------------------------
Key: TEIIDDES-1981
URL:
https://issues.jboss.org/browse/TEIIDDES-1981
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 8.2
Reporter: Mark Drilling
Assignee: Mark Drilling
Fix For: 8.5
Attachments: MongoCP.xml, plugin.properties, plugin.xml
Attempt to model and query MongoDB in Designer
1) Mongo CP is not available in default JBDS
2) We cannot set the Mongo CP on source model - not supported. We do not have a
connectionProvider
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)