[
https://issues.jboss.org/browse/TEIID-1605?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1605.
-----------------------------------
Fix Version/s: 7.4.1
Resolution: Done
The quick summary is that in 7.1.1 a custom translator is needed to 1. declare pushdown
support, 2. use a functionmodifier or other logic to alter the udf name to the source
expected package qualified form.
For 7.4.1 the changes committed for this issue allow a function model (created in Designer
7.4) to contain a function with a name matching the full source name. A custom translator
is still required to declare support for the function.
More generally even though we have new function abilities, such as multiple function
models, or the ability to declare source metadata/translator pushdown functions. There is
still a weak link in translators declaring function support. While declaring support is
handled automatically for translator pushdown functions, it is still just name, not
signature, based. Also even though you can have multiple schemas with functions, the
expectation is that the function support uses only the short name. This effectively
prevents you from having two udfs with the same name (even though that's perfectly
valid with two different models).
Unable to call a function that is defined within a package in oracle
--------------------------------------------------------------------
Key: TEIID-1605
URL:
https://issues.jboss.org/browse/TEIID-1605
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Fix For: 7.4.1
Unable to call a function that is defined within a package in oracle.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira