February 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2374) OracleExecutionFactory should indicate support of common table expressions for 9.2 or later

by Johnathon Lee (JIRA)

Johnathon Lee created TEIID-2374: ------------------------------------ Summary: OracleExecutionFactory should indicate support of common table expressions for 9.2 or later Key: TEIID-2374 URL: https://issues.jboss.org/browse/TEIID-2374 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 7.7.4, 8.2 Reporter: Johnathon Lee Assignee: Steven Hawkins OracleExecutionFactory is not marked as supporting common table expressions. It should be returning as supported for a database version of 9.2 or later. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2371) Provide a callback when there are no results for a query incase of asynchronous queries

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2371?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2371: --------------------------------------- > So as beforeNextExecution gets called in between the executions this doesn't perfectly identify the empty result set. A "has results flag" or a counter of the rows processed in onRow will identify if the results were empty when beforeNextExecution is called. You could even use the ResultSet.getRow() call - keeping in mind that it have a dummy row for each execution that identifies the end of results. None of these approaches would fail to detect empty results. > Provide a callback when there are no results for a query incase of asynchronous queries > --------------------------------------------------------------------------------------- > > Key: TEIID-2371 > URL: https://issues.jboss.org/browse/TEIID-2371 > Project: Teiid > Issue Type: Feature Request > Reporter: Vineela Gampa > Assignee: Steven Hawkins > Attachments: EmptyResultSetAsyncTest.java, ExecuteAsyncContinously.java > > > When a query doesn,t return results , please provide a callback method indicating end of results. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2371) Provide a callback when there are no results for a query incase of asynchronous queries

by Vineela Gampa (JIRA)

[ https://issues.jboss.org/browse/TEIID-2371?page=com.atlassian.jira.plugin... ] Vineela Gampa commented on TEIID-2371: -------------------------------------- Hi Steve, Please take a look at com.ca.chorus.db.async.ExecuteAsyncContinously.continuouslyWhenData(). We have a feature called autoRefresh where the data is refreshed on UI every minute. So we dont close the statement until the user turns off autoRefresh(thats when we cancel the qeury and close the statement). In my testcase beforeNextExecution gets called in between the executions. when the query is getting executed - 1) onRow gets called 2)beforeNextExecution gets called between the executions 2) next continous execution starts - on row gets triggered So as beforeNextExecution gets called in between the executions this doesn't perfectly identify the empty result set. To identify emptyResultset this is the approach iam planning on - if on row is not called and beforeNextExecution gets called(for continous executions)/onComplete(incase of noncontinous) , then i treat it as an empty resultset. Do you think this would fail in any scenario ? > Provide a callback when there are no results for a query incase of asynchronous queries > --------------------------------------------------------------------------------------- > > Key: TEIID-2371 > URL: https://issues.jboss.org/browse/TEIID-2371 > Project: Teiid > Issue Type: Feature Request > Reporter: Vineela Gampa > Assignee: Steven Hawkins > Attachments: EmptyResultSetAsyncTest.java, ExecuteAsyncContinously.java > > > When a query doesn,t return results , please provide a callback method indicating end of results. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2371) Provide a callback when there are no results for a query incase of asynchronous queries

by Vineela Gampa (JIRA)

[ https://issues.jboss.org/browse/TEIID-2371?page=com.atlassian.jira.plugin... ] Vineela Gampa updated TEIID-2371: --------------------------------- Attachment: ExecuteAsyncContinously.java > Provide a callback when there are no results for a query incase of asynchronous queries > --------------------------------------------------------------------------------------- > > Key: TEIID-2371 > URL: https://issues.jboss.org/browse/TEIID-2371 > Project: Teiid > Issue Type: Feature Request > Reporter: Vineela Gampa > Assignee: Steven Hawkins > Attachments: EmptyResultSetAsyncTest.java, ExecuteAsyncContinously.java > > > When a query doesn,t return results , please provide a callback method indicating end of results. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2373) Strict LIMITs are not properly enforced

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2373?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2373. ----------------------------------- Resolution: Done Corrected the node constant is_strict to is_non_strict to reflect a safe default and updated the pushing logic to copy the flag from the parent in all cases. > Strict LIMITs are not properly enforced > --------------------------------------- > > Key: TEIID-2373 > URL: https://issues.jboss.org/browse/TEIID-2373 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.6 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > The notion of a strict limit introduced by TEIID-1806 - is not strictly enforced when an unordered limit is first pushed across a union. The result may be fewer rows than expected if the limit is then pushed across a select node. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2373) Strict LIMITs are not properly enforced

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2373: ------------------------------------- Summary: Strict LIMITs are not properly enforced Key: TEIID-2373 URL: https://issues.jboss.org/browse/TEIID-2373 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.3 The notion of a strict limit introduced by TEIID-1806 - is not strictly enforced when an unordered limit is first pushed across a union. The result may be fewer rows than expected if the limit is then pushed across a select node. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2370) Pushdown LIMIT in cross product joins

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2370?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2370. ----------------------------------- Resolution: Done Refined the code suggested in the forum posting to account for inner joins converted to cross joins and to limit the left side of outer joins. > Pushdown LIMIT in cross product joins > ------------------------------------- > > Key: TEIID-2370 > URL: https://issues.jboss.org/browse/TEIID-2370 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Mark Addleman > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.3 > > > Pushdown LIMIT clause in cross product joins. Queries of form > SELECT t1.a FROM t1, t2 LIMIT 10 > Produce a plan like this: > LIMIT 10 > CROSS JOIN > Access: SELECT t1.a FROM t1 LIMIT 10 > Access: SELECT 1 FROM t2 LIMIT 10 > See https://community.jboss.org/thread/220834?tstart=0 for a little more detail -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2370) Pushdown LIMIT in cross product joins

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2370?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2370: ---------------------------------- Issue Type: Enhancement (was: Feature Request) Fix Version/s: 8.3 Affects Version/s: (was: 8.1) Priority: Minor (was: Critical) > Pushdown LIMIT in cross product joins > ------------------------------------- > > Key: TEIID-2370 > URL: https://issues.jboss.org/browse/TEIID-2370 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Mark Addleman > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.3 > > > Pushdown LIMIT clause in cross product joins. Queries of form > SELECT t1.a FROM t1, t2 LIMIT 10 > Produce a plan like this: > LIMIT 10 > CROSS JOIN > Access: SELECT t1.a FROM t1 LIMIT 10 > Access: SELECT 1 FROM t2 LIMIT 10 > See https://community.jboss.org/thread/220834?tstart=0 for a little more detail -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2372) Providing functionality to set source table cardinality when metadata loaded

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2372?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2372: ------------------------------------- Jack, 8.3 is kind of closing in, will see if we can fit in. > Providing functionality to set source table cardinality when metadata loaded > ---------------------------------------------------------------------------- > > Key: TEIID-2372 > URL: https://issues.jboss.org/browse/TEIID-2372 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.2 > Reporter: Jack Ma > Assignee: Steven Hawkins > > Want to have a easy way to set the source table cardinality when source model metadata loaded -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2372) Providing functionality to set source table cardinality when metadata loaded

by Jack Ma (JIRA)

[ https://issues.jboss.org/browse/TEIID-2372?page=com.atlassian.jira.plugin... ] Jack Ma commented on TEIID-2372: -------------------------------- Like Maresh indicated that we could use something like: ALTER TABLE/VIEW ... ADD OPTION CARDINALITY 10000 To set the cardinality at source model > Providing functionality to set source table cardinality when metadata loaded > ---------------------------------------------------------------------------- > > Key: TEIID-2372 > URL: https://issues.jboss.org/browse/TEIID-2372 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.2 > Reporter: Jack Ma > Assignee: Steven Hawkins > > Want to have a easy way to set the source table cardinality when source model metadata loaded -- 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

11 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2013