[
https://issues.jboss.org/browse/TEIIDDES-992?page=com.atlassian.jira.plug...
]
Bernd Groh commented on TEIIDDES-992:
-------------------------------------
According to the manual:
http://docs.jboss.org/teiid/7.4.0.Final/developer-guide/en-US/html/udfs.h...
It is necessary, in order to make a source supported function available for use, to extend
the connector class. While you don't need to write a method that contains the
function’s logic, you still need to extend the connector class by adding the according
function(s) as supported pushdown function(s). You then need to package your extended
connector and deploy it to the server. In other words, you have to deal with Java code and
packaging jar files, and getting these jar files deployed to the server, if all you want
to do is to use a particular pushdown function in your virtual database designs.
Is this correct? Or have I misunderstood things?
Allow the use of pushdown functions without requiring Java
programming
----------------------------------------------------------------------
Key: TEIIDDES-992
URL:
https://issues.jboss.org/browse/TEIIDDES-992
Project: Teiid Designer
Issue Type: Feature Request
Reporter: Bernd Groh
Currently, in order to use a database function, even if pushdown is required, it is still
necessary to add the function interface to a Java class within the connector, and the
connector then must be deployed to the server in order to allow for this pushdown function
to be used within the Designer. This creates a lot of extra effort every time you want to
make use of a new database function. Particularly, given the schema designer doesn't
necessarily have access to either the connector code or the server, and then must involve
other parties simply to be able to use an additional database function. It would be very
beneficial to speedy schema development if that was not necessary, and if, say, the
interface could be defined on the Designer side, added to the VDB, and then deployed as
part of the VDB.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira