[ https://issues.jboss.org/browse/TEIID-2111?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2111: --------------------------------------- The workaround would be to add an array_con(object... ) vararg udf to construct array values to pass into the procedure as an object argument. -- 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-2111?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2111: --------------------------------------- Added the initial support. DDL metadata can now use the VARIADIC keyword instead of IN on the last (non return/result set) parameter to a procedure or function to indicate that varargs are expected. For example: create foreign procedure proc (x integer, VARIADIC z integer) returns (x string); Within Teiid we'll treat the vararg parameter as an array. Within a virtual procedure we will also correctly handle typed access to the parameter array using array_get and the [] operator. The vararg array can be passed as a VARIADIC parameter to either functions or procedures. A pushdown procedure will have the parameter array unwound into separate IN parameter arguments, with the expectation the the source procedure is also VARIADIC. Design time support will still need to be validated. The docs also still need updating. An implementation note: we do not have teiid types for array types, rather we just use the corresponding java array type with the string name type[]. Also our handling of functions and procedures is different with respect to varargs. Function support predated any array type support so it's based around repeated parameters that are turned into an array for function invocation. Procedures keep track of parameters either by name or position (which then cannot conflict with result set columns) so repeating the parameter is not possible. I'll probably look to convert the function handling into the procedure style for consistency and also so that the function parameter typing is done up front - rather than constantly referencing back to the datatypemanager. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-2111?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2111. ----------------------------------- Resolution: Done Marking as resolved on the teiid side. There is still additional cleanup work that can be done under general array support. Since arrays are not formally supported the docs don't mention that you can pass an array value as the VARIADIC argument, such as shown in the unit tests: create foreign procedure proc (x integer, VARIADIC z integer); create virtual procedure vproc (x integer, VARIADIC z integer) returns integer as begin "return" = z[2] + array_length(z); call proc(x, z); end; note that z is being passed directly to proc in the procedure definition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-2111?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2111. --------------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira