February 2013 - teiid-issues - Jboss List Archives

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

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2372?page=com.atlassian.jira.plugin... ] SBS JIRA Integration updated TEIID-2372: ---------------------------------------- Forum Reference: https://community.jboss.org/message/795455#795455 > 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, 3 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: -------------------------------- This issue is a subset of issue teiid-992. > 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, 3 months

1
0
0 / 0

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

by Jack Ma (JIRA)

Jack Ma created TEIID-2372: ------------------------------ Summary: 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, 3 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 resolved TEIID-2371. ----------------------------------- Resolution: Duplicate Issue See TEIID-2257 note that in your test case you shouldn't expect to see onRow as no rows are returned. See the beforeNextExecution method on the ContinuousStatementCallback. > 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 > > > 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, 3 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)

Vineela Gampa created TEIID-2371: ------------------------------------ Summary: 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 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, 3 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: EmptyResultSetAsyncTest.java Testcase for the issue. > 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 > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-992) Improve update of source costing statistics

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-992?page=com.atlassian.jira.plugin.... ] SBS JIRA Integration updated TEIID-992: --------------------------------------- Forum Reference: https://community.jboss.org/message/795455#795455 > Improve update of source costing statistics > ------------------------------------------- > > Key: TEIID-992 > URL: https://issues.jboss.org/browse/TEIID-992 > Project: Teiid > Issue Type: Sub-task > Components: Misc. Connectors, Query Engine > Reporter: Marc Shirley > Assignee: Ramesh Reddy > > It is very important that we support the ability to update source statistics at runtime. This is important due to the changing nature of read/write sources and differences between a development data source and a production data source. > The following options should be possible: > 1) Update model/source statistics on VDB deployment. > 2) Update model/source statistics on connector startup. > 3) Update model/source statistics on at a scheduled time. > 4) Update model/source statistics upon a manual request. > case 5920 -- 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, 3 months

1
0
0 / 0

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

by Mark Addleman (JIRA)

Mark Addleman created TEIID-2370: ------------------------------------ Summary: Pushdown LIMIT in cross product joins Key: TEIID-2370 URL: https://issues.jboss.org/browse/TEIID-2370 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 8.1 Reporter: Mark Addleman Assignee: Steven Hawkins Priority: Critical 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2361) The current MAX String size is 4000, add the ability to configure when larger sizes are used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2361?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2361: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=896305 > The current MAX String size is 4000, add the ability to configure when larger sizes are used > -------------------------------------------------------------------------------------------- > > Key: TEIID-2361 > URL: https://issues.jboss.org/browse/TEIID-2361 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.3 > > > The MAX String size is currently 4000. After a discussion with Steve, he indicated a more common default might be 16k, and also add the ability to configure the size when a data source is being used that contains large sizes. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2361) The current MAX String size is 4000, add the ability to configure when larger sizes are used

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2361?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2361: --------------------------------------- Regardless of the version Teiid will try to limit in-memory strings to the max size via truncation, whether that is from function evaluation, conversions, etc. However not every source will have direct string values checked against the max (this is why I refer to it as a nominal not a hard maximum) this allows for some simple passthrough scenarios to work with strings larger than the max. Sources (not Teiid) may throw exceptions depending upon their handling of larger strings. We may need to incorporate some additional translator logic as needed. > The current MAX String size is 4000, add the ability to configure when larger sizes are used > -------------------------------------------------------------------------------------------- > > Key: TEIID-2361 > URL: https://issues.jboss.org/browse/TEIID-2361 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.3 > > > The MAX String size is currently 4000. After a discussion with Steve, he indicated a more common default might be 16k, and also add the ability to configure the size when a data source is being used that contains large sizes. -- 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, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2013