[teiid-issues] [JBoss JIRA] (TEIID-5130) Document/refine behavior of treating result parameter as the first parameter

[Jan Stastny (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538963#comment-13538963 ] 

Jan Stastny commented on TEIID-5130:
------------------------------------

[~jolee], [~shawkins]
I can't really tell. I don't know exactly, what is the expected behavior. What I tried (and the result does not follow my expectations) is:
# set the property to false via cli (no reload was requested)
# deploy the vdb above
# waiting for the deployment to fail

> Document/refine behavior of treating result parameter as the first parameter
> ----------------------------------------------------------------------------
>
>                 Key: TEIID-5130
>                 URL: https://issues.jboss.org/browse/TEIID-5130
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: Query Engine
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 10.0, 9.3.5, 8.12.12.6_4
>
>
> DDL and metadata import make the assumption that the return parameter is the first in the underlying metadata (in part to ensure support of varargs), but we still allowed the result parameter to appear anywhere in the parameter list as to maintain backwards compatibility with legacy/Designer ddl.  However in index metadata there is slightly different behavior in that the result parameter remains in it's original position.
> We need to clarify this behavior - more documentation, enforce/validate that the result parameter is first in ddl, or perform the same reordering for index metadata.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)