[ https://issues.jboss.org/browse/TEIID-1796?page=com.atlassian.jira.plugin... ] Paul Nittel updated TEIID-1796: ------------------------------- Attachment: PushDownTest_MPS.zip Model Project Set containing the stuff I tested with. -- 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-1796?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1796. ----------------------------------- Fix Version/s: (was: 8.0) Resolution: Won't Fix The is actually more complicated than it seems, since the translator function logic relies on function names to utilize FunctionModifiers. Changing that for logic is not appropriate for just this issue. The only circumstance where this behavior would even be required (beyond supported the simple abstraction use case) would be if the source function name contained a '.' period, which could be worked around by extending the translator with a FunctionModifier. We do currently use name in source for translator declared pushdown functions. Any other scalar functions are effectively virtual (as the model is not tied to a particular source) so the name in source, just like with virtual model, is no longer meaningful. If/whenever we combine the function/relational metamodels we could revisit this. -- 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