[JBoss JIRA] (TEIID-2146) Dependent join independent dup removal issue
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2146:
-------------------------------------
Summary: Dependent join independent dup removal issue
Key: TEIID-2146
URL: https://issues.jboss.org/browse/TEIID-2146
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Blocker
Fix For: 8.1
If a dependent join uses columns from the independent side beyond the join predicates and has unique values with duplicates for the predicate value from the independent side, then the duplicate removal will fail to remove the duplicates, since it is mistakenly using all columns.
If the duplicates then span multiple dependent queries, such as would be the case with large dependent joins or when a source is used with limited value pushdown (such as sybase), then the join result can be incorrect with duplicate rows.
--
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
12 years, 1 month
[JBoss JIRA] (TEIID-2200) Web Consoel: Table page size
by Heiko Braun (JIRA)
Heiko Braun created TEIID-2200:
----------------------------------
Summary: Web Consoel: Table page size
Key: TEIID-2200
URL: https://issues.jboss.org/browse/TEIID-2200
Project: Teiid
Issue Type: Feature Request
Components: AdminApi
Reporter: Heiko Braun
Assignee: Ramesh Reddy
reduce the number of items per page. 30 is typically too much. it defeats the purpose of the pager and will lead to long vertical scrolling. 8 is typically a good number
--
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
12 years, 1 month
[JBoss JIRA] (TEIID-2188) When using CONCAT2(x, y), can the source query be changed to not include the CASE statements and let Oracle do the NULL compare
by Van Halbert (JIRA)
Van Halbert created TEIID-2188:
----------------------------------
Summary: When using CONCAT2(x, y), can the source query be changed to not include the CASE statements and let Oracle do the NULL compare
Key: TEIID-2188
URL: https://issues.jboss.org/browse/TEIID-2188
Project: Teiid
Issue Type: Enhancement
Components: Embedded
Affects Versions: 7.4.4
Reporter: Van Halbert
Assignee: Steven Hawkins
When CONCAT2(x, y) is used, the rewritten query is very verbose in adding a CASE statement to check for nulls. Can the rewritten query not include the CASE statements and just let Oracle do the compare, because it can do it more efficiently within the CONCAT call?
Example:
select concat2(f1,f2) from table1
results in
SELECT c_0 FROM (SELECT CASE WHEN to_char(g_0.f1) IS NULL AND g_0.f2 IS NULL THEN NULL ELSE concat(nvl(to_char(g_0.f1), ''), nvl(g_0.f2, '')) END AS c_0 FROM table1 g_0)
--
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
12 years, 1 month