[teiid-issues] [JBoss JIRA] Updated: (TEIID-119) physical procedural mapping results in inconsistent results

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy updated TEIID-119:
-------------------------------

          Component/s: Query Engine
        Fix Version/s: 6.1.0
    Affects Version/s: 6.x


> physical procedural mapping results in inconsistent results
> -----------------------------------------------------------
>
>                 Key: TEIID-119
>                 URL: https://jira.jboss.org/jira/browse/TEIID-119
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: 6.x
>            Reporter: Marc Shirley
>            Assignee: Steven Hawkins
>            Priority: Critical
>             Fix For: 6.1.0
>
>
> Defect Tracker #24951: testing a query with multiple physical procedure calls using the new mapping style results in inconsistent/incorrect results. As a test case, sptest6, a physical procedure that doubles the integer value passed into it, was called twice in a view transformation, with a result set consisting of the the source, input, and result values for each call to the procedure. 2 issues were seen: 
> 1) Source and input value columns only showed the value of the last input parameter for all rows. 
> 2) The result values for the first procedure call were correct for every row, but the result values for the second procedure call were the same for every row (it only showed the last result value calculated for all the rows). 
> After mapping the physical procedure to a virtual procedure, no issue was seen.  Issue can be seen in "view.two_bqt_sptest6_test" in attached vdb, or at mm://sluxtech09:55391 (http://sluxtech09:18391).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira