[
https://issues.jboss.org/browse/TEIIDDES-1981?page=com.atlassian.jira.plu...
]
Mark Drilling resolved TEIIDDES-1981.
-------------------------------------
Resolution: Done
By exposing the Mongo CP we are not inventing anything new - we are just exposing the JBDS
profiles that have already been defined.
No, we do not have a Mongo importer, but exposing the MongoCP allows the existing preview
and vdb deployment functionality to work without forcing the user through a lot of
unnecessary steps. The 'JBoss DS' CP only works if the source has first been
created on the server. With a specific connection profile, the current preview and vdb
execution use cases can auto deploy the source, therefore no need to create it in a
separate operation.
We fully expect to re-work in a future release but have discussed and decided this is the
best approach until then.
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)