[ https://issues.jboss.org/browse/TEIID-1947?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1947: ------------------------------------- May be better option is having Designer give an option to select the translator to be used with the every source model with any kind of import. Then on teiid server we can use XML based translator deployment to configure these extended properties. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1947?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1947: ------------------------------------- Irrespective of the Translator override we need to be able select a translator for every import. choose some by default, but let user have capability to change. In Teiid server, there is a option to add overridden translator by specifying a XML fragment just like Designer does in the vdb.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1947?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1947: --------------------------------------- Users currently import without a Teiid server, however that should be considered a legacy approach. We should strive toward bringing the notion of designer imported metadata through translators - as the dynamic vdb case already does. All of the non-Teiid imported Designer metadata is really in service to Teiid and contains Teiid specific constructs - some that are intimately tied to specific translators. As we move further along with custom translators, it becomes imperative that customization is driven by the translator itself. Involving designer specific importers, additional meds, etc., are really just complications from a developers perspective who could much more naturally drive the behavior from the custom translator. So to circle back to the existing issue. We do need to allow users to tweak preview behavior, however as long as the import logic is performed by Designer code it's a moot point about setting translator override values at import time since no translator is involved. If making the effort to change the preview behavior depends on TEIIDDES-1079 and that is slated for 8.0, then we'll have to let stackholders weigh in on the prioritization. I would also vote to convert this issue into a more general "change preview behavior" issue and move it over to Designer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira