[
https://issues.jboss.org/browse/TEIIDDES-1981?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIIDDES-1981:
----------------------------------------
Ok, These are two different things,
1) What you are getting at is cleaning up the entire connection profile work across all
the JBoss AS projects and coming up with more intuitive one to use
2) What I am saying is much more smaller in scope until we go Komodo (as I understand this
is at-least 1-2 yrs away to be in product)
- Do not add *any* connection profiles that you do not have custom importers for
- The connection profiles that we did add before "JBoss DS" for translators
that use "Teiid Connection Importer", remove them and make user to use
"JBoss DS" instead. This an all an effort to keep Designer changes to ZERO when
a new translator/source is added.
The other comment was how to improve the usability of the Teiid Connection Importer.
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)