Major We are currently mapping procedures and functions defined by ddl to odata functions/actions. The latter is due that the function is represented in our system metadata as a procedure. We need to decide if all functions should be mapped. There's also the notion of a composable function that could be helpful.
- relates to
-
TEIID-5725 Please improve documentation on definition of stored procedures, virtual functions and virtual procedures
-
- Resolved
-
[TEIID-5736] General odata function mapping
Steven Hawkins
added a comment - Also it appears that odata does not account for varargs, but that will need to be addressed by a separate issue.
Steven Hawkins
added a comment - Also it appears that odata does not account for varargs, but that will need to be addressed by a separate issue. 
After looking into this more, it is probably not worth the effort. Getting the metadata added is straight-forward, but the invocation logic would be all new (sql generation, parameter handling, etc.). The workaround of using a procedure to expose functions will be noted in the odata docs.