[JBoss JIRA] (TEIIDDES-3069) odata4 fails to return data on top of mongoDB view model
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3069?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-3069:
------------------------------------------
Given the behavior of Designer to leave the default length of 0, TEIID-5111 will treat that as the default/max for index metadata. However TEIID-5112 will expect proper length values in DDL.
For 6.4 or older branches TEIID-5111 can be pulled back if we want, but it's not a blocker as the workaround is to simply alter the length value for affected columns in Designer.
> odata4 fails to return data on top of mongoDB view model
> ---------------------------------------------------------
>
> Key: TEIIDDES-3069
> URL: https://issues.jboss.org/browse/TEIIDDES-3069
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Environment: Noticed in JDV 6.3.4
> Reporter: Michael Echevarria
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 11.2
>
> Attachments: Screenshot from 2017-03-28 15-38-25.png, Screenshot from 2017-03-28 15-38-32.png, Screenshot from 2017-03-28 15-38-46.png, Screenshot from 2017-03-28 15-38-56.png, designer-length-added.png, mongo-view-error.png, odata2-works.png, odata4-error.png, odata4-with-length-changed.png
>
>
> Description of problem:
> Accessing either an exclusive view model or combined view model for a mongoDB datasource via odata4 results in an error.
> The data returns via odata2, jdbc and preview in the designer
> Version-Release number of selected component (if applicable):
> JDV 6.3.4
> Actual results:
> Property mapping error
> Expected results:
> Model data
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3126) Set operations and parenthesis
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3126?page=com.atlassian.jira.plu... ]
Van Halbert closed TEIIDDES-3126.
---------------------------------
Resolution: Duplicate Issue
> Set operations and parenthesis
> ------------------------------
>
> Key: TEIIDDES-3126
> URL: https://issues.jboss.org/browse/TEIIDDES-3126
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Blocker
>
> Using Teiid 9.2.2 with postgresql, I issue a query structured like this:
>
> (a
> UNION ALL
> b
> UNION ALL
> c)
> INTERSECT
> d
>
> All queries are from a single database.
> This query does not give back the expected result.
> In the plan, I see the query printed with no parenthesis around the unions:
> a UNION ALL b UNION ALL c INTERSECT d
> This gives the same result as the query submitted with no parens in it (the intersect of c and d is unioned with a union b.
> The expepeted result is to preserve the paren so that the intersect is performed against the union of all three tables.
> As a note, using UNION instead of UNION ALL did not preserve the parens, either.
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3126) Set operations and parenthesis
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3126?page=com.atlassian.jira.plu... ]
Van Halbert moved TEIID-5113 to TEIIDDES-3126:
----------------------------------------------
Project: Teiid Designer (was: Teiid)
Key: TEIIDDES-3126 (was: TEIID-5113)
Component/s: Editors
(was: Connector API)
(was: Query Engine)
Fix Version/s: (was: 10.0)
(was: 9.3.4)
(was: 9.2.7)
> Set operations and parenthesis
> ------------------------------
>
> Key: TEIIDDES-3126
> URL: https://issues.jboss.org/browse/TEIIDDES-3126
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Blocker
>
> Using Teiid 9.2.2 with postgresql, I issue a query structured like this:
>
> (a
> UNION ALL
> b
> UNION ALL
> c)
> INTERSECT
> d
>
> All queries are from a single database.
> This query does not give back the expected result.
> In the plan, I see the query printed with no parenthesis around the unions:
> a UNION ALL b UNION ALL c INTERSECT d
> This gives the same result as the query submitted with no parens in it (the intersect of c and d is unioned with a union b.
> The expepeted result is to preserve the paren so that the intersect is performed against the union of all three tables.
> As a note, using UNION instead of UNION ALL did not preserve the parens, either.
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3125) Set operations and parenthesis
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3125?page=com.atlassian.jira.plu... ]
Steven Hawkins reassigned TEIIDDES-3125:
----------------------------------------
Description:
Entering a query such as:
(a
UNION ALL
b
UNION ALL
c)
INTERSECT
d
The query is displayed as
a UNION ALL b UNION ALL c INTERSECT d
was:
Using Teiid 9.2.2 with postgresql, I issue a query structured like this:
(a
UNION ALL
b
UNION ALL
c)
INTERSECT
d
All queries are from a single database.
This query does not give back the expected result.
In the plan, I see the query printed with no parenthesis around the unions:
a UNION ALL b UNION ALL c INTERSECT d
This gives the same result as the query submitted with no parens in it (the intersect of c and d is unioned with a union b.
The expepeted result is to preserve the paren so that the intersect is performed against the union of all three tables.
As a note, using UNION instead of UNION ALL did not preserve the parens, either.
Assignee: Barry LaFond (was: Steven Hawkins)
Converting to a designer issue as the same problem should exist in the forked teiid code and probably the display node framework.
> Set operations and parenthesis
> ------------------------------
>
> Key: TEIIDDES-3125
> URL: https://issues.jboss.org/browse/TEIIDDES-3125
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Reporter: Mike Higgins
> Assignee: Barry LaFond
> Priority: Blocker
>
> Entering a query such as:
>
> (a
> UNION ALL
> b
> UNION ALL
> c)
> INTERSECT
> d
> The query is displayed as
> a UNION ALL b UNION ALL c INTERSECT d
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3125) Set operations and parenthesis
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3125?page=com.atlassian.jira.plu... ]
Steven Hawkins moved TEIID-5110 to TEIIDDES-3125:
-------------------------------------------------
Project: Teiid Designer (was: Teiid)
Key: TEIIDDES-3125 (was: TEIID-5110)
Component/s: Transformations
(was: Connector API)
(was: Query Engine)
Fix Version/s: (was: 10.0)
(was: 9.3.4)
(was: 9.2.7)
> Set operations and parenthesis
> ------------------------------
>
> Key: TEIIDDES-3125
> URL: https://issues.jboss.org/browse/TEIIDDES-3125
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Reporter: Mike Higgins
> Assignee: Steven Hawkins
> Priority: Blocker
>
> Using Teiid 9.2.2 with postgresql, I issue a query structured like this:
>
> (a
> UNION ALL
> b
> UNION ALL
> c)
> INTERSECT
> d
>
> All queries are from a single database.
> This query does not give back the expected result.
> In the plan, I see the query printed with no parenthesis around the unions:
> a UNION ALL b UNION ALL c INTERSECT d
> This gives the same result as the query submitted with no parens in it (the intersect of c and d is unioned with a union b.
> The expepeted result is to preserve the paren so that the intersect is performed against the union of all three tables.
> As a note, using UNION instead of UNION ALL did not preserve the parens, either.
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIIDDES-3103) Execute VDB in the Guides doesn't work
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3103?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-3103.
----------------------------------
Resolution: Cannot Reproduce
> Execute VDB in the Guides doesn't work
> --------------------------------------
>
> Key: TEIIDDES-3103
> URL: https://issues.jboss.org/browse/TEIIDDES-3103
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1
> Environment: Fedora 26
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 11.1.1
>
> Attachments: guides.mkv, screenshot.png
>
>
> Last step (execute VDB) in the first guide (Model JDBC Source) doesn't work. After click on the "Execute VDB" shows wizard for choosing VDB (screenshot1). After click OK, VDB is not deployed.
> I noticed that it doesn't work in the other guides as well.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months