[teiid-issues] [JBoss JIRA] Resolved: (TEIID-231) Ability to support Connector Level UDF functions in the System

[Ramesh Reddy (JIRA)]

     [ https://jira.jboss.org/browse/TEIID-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Reddy resolved TEIID-231.
--------------------------------

    Resolution: Done


There are lot of functionality changed from the time this jira logged till now with the Teiid project. The initial goal still was required UDF functions with the Translators.

Taking Larry's suggestions from above, Teiid already provides a UDF model to be packaged with VDB, where the UDF functions are local to the VDB. There is no global UDF function model allowed in the current version of the Teiid.

This JIRA addresses both Larry and SteveH comments from above. 
1) The Schema model exposed by the "Translator" metadata is now capable of defining the "Function". i.e. Required API objects have been added to the Translator API. Depending upon if this metadata used by a view model or source model, you can define the UDF support at that level. These functions are automatically added Function Library.

2) Translators now have a new capability to define "pushdown" functions, which are then injected into the FunctionLibrary, just as how system functions. With a custom Translator one can define some "pushdown" functions, those will be automatically used by the query planning code to use appropriately.

Note that the UDF added through above functionality are added using model's name as the namespace. For example if model name is "accounts" and you added a function "payable" then the added UDF name will be

"accounts.payable"

The queries are recommended to use the "fully qualified name", however resolver is smart enough to accept the partial name too, if there are not any conflicts.

In the current form, Designer would still will not be able to resolve the added UDF functions through the Translator, until it modifies how it loads the Function Library.

Currently to add UDFs in the Translator level require code changes, there will not be any feature to support addition of new UDFs based an XMI file or property file. When Teiid adopts SQL/MED way of defining the metadata  that will provide a external way to define the UDFs.

> Ability to support Connector Level UDF functions in the System
> --------------------------------------------------------------
>
>                 Key: TEIID-231
>                 URL: https://jira.jboss.org/browse/TEIID-231
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Connector API, Query Engine
>    Affects Versions: 6.0.0
>            Reporter: Ramesh Reddy
>            Assignee: Ramesh Reddy
>             Fix For: 7.3
>
>
> Currently we have UDF and Connector capabilities to define some custom functions in supported by a connector, however this is not seem less to deploy along with the connector, as connector functions do not support any parameters or design tools to define/declare them in CDK. We need a way to define and develop functions supported by a connector. 
> Suggestions.
> 1) Use designer to define capabilities in a XMI file and attach with the connector, and let the server or MMQuery load these XMI files dynamically into the engine.
> 2) 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira