[JBoss JIRA] (TEIID-4144) Mismanagement of output columns in ruleimplementjoinstrategy
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4144?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4144.
-----------------------------------
Resolution: Done
Switched the project to be added as a parent of the source node - which is the logical point where the sort is inserted and the output columns are being manipulated.
> Mismanagement of output columns in ruleimplementjoinstrategy
> ------------------------------------------------------------
>
> Key: TEIID-4144
> URL: https://issues.jboss.org/browse/TEIID-4144
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.0, 8.12.5, 8.13.1, 8.7.3.6_2
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5, 8.13.4
>
>
> Related to TEIID-3973 - the fix introduced a situation where if the sort node is not added and a join expression is used and there are intervening nodes, then the output columns are not correctly managed. The result is a similar value not found exception.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-4144) Mismanagement of output columns in ruleimplementjoinstrategy
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4144:
-------------------------------------
Summary: Mismanagement of output columns in ruleimplementjoinstrategy
Key: TEIID-4144
URL: https://issues.jboss.org/browse/TEIID-4144
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.13.1, 9.0, 8.12.5, 8.7.3.6_2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.0, 8.12.5, 8.13.4
Related to TEIID-3973 - the fix introduced a situation where if the sort node is not added and a join expression is used and there are intervening nodes, then the output columns are not correctly managed. The result is a similar value not found exception.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-4143) Wrong Content-Type in error response from odata
by Andrej Šmigala (JIRA)
Andrej Šmigala created TEIID-4143:
-------------------------------------
Summary: Wrong Content-Type in error response from odata
Key: TEIID-4143
URL: https://issues.jboss.org/browse/TEIID-4143
Project: Teiid
Issue Type: Bug
Components: OData
Affects Versions: 8.12.x
Reporter: Andrej Šmigala
Assignee: Steven Hawkins
Priority: Blocker
When submitting an odata request that causes an error on server side, the response has the Content-Type header set to just "application", which causes clients to fail.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-4142) Use a universal procedure to update Mat View
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4142?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-4142:
-------------------------------
Description:
Base on current design,
* update Internal Mat view use sysadmin.refreshmatview()
* update external Mat view use sysadmin.loadmatview()
But in some time, we need a universal procedure which can update both internal and external Mat View.
was:
Due to current design,
* update Internal Mat view use sysadmin.refreshmatview()
* update external Mat view use sysadmin.loadmatview()
But in some time, we need a universal procedure which can update both internal and external Mat View.
> Use a universal procedure to update Mat View
> --------------------------------------------
>
> Key: TEIID-4142
> URL: https://issues.jboss.org/browse/TEIID-4142
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 9.0
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.0
>
>
> Base on current design,
> * update Internal Mat view use sysadmin.refreshmatview()
> * update external Mat view use sysadmin.loadmatview()
> But in some time, we need a universal procedure which can update both internal and external Mat View.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-4142) Use a universal procedure to update Mat View
by Kylin Soong (JIRA)
Kylin Soong created TEIID-4142:
----------------------------------
Summary: Use a universal procedure to update Mat View
Key: TEIID-4142
URL: https://issues.jboss.org/browse/TEIID-4142
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Affects Versions: 9.0
Reporter: Kylin Soong
Assignee: Kylin Soong
Fix For: 9.0
Due to current design,
* update Internal Mat view use sysadmin.refreshmatview()
* update external Mat view use sysadmin.loadmatview()
But in some time, we need a universal procedure which can update both internal and external Mat View.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months