June 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Moved: (TEIID-1638) Add ability to query parent record info from child table query without joins for the Salesforce Translator

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1638?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-3110 to TEIID-1638: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1638 (was: SOA-3110) Affects Version/s: 7.1.1 (was: 5.1.0 GA) Component/s: Salesforce Connector (was: EDS) Security: (was: Public) > Add ability to query parent record info from child table query without joins for the Salesforce Translator > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-1638 > URL: https://issues.jboss.org/browse/TEIID-1638 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Labels: eds, salesforce > > Salesforce.com SOQL supports selecting parent record value through reference key name. > We need to query parent record info from child table query. For example, if I have column parentid in Contact object which is reference key to account object, I can do in SOQL in salesforce.com something like this. > Select c.Id, c.Name, c.AccountId, c.Account.Name > from Contact c > But if i want to do the same in EDS, I have to use Relationship Queries (join of two tables Account and Contact) which is huge impact on performance -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-97) add proper SQLState for timeout/cancel

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-97?page=com.atlassian.jira.plugin.s... ] Steven Hawkins resolved TEIID-97. --------------------------------- Assignee: Steven Hawkins Resolution: Done Ensured that the server will send an exception with sqlstate cancel code. Also updated our exceptions to use the underlying sqlstate as the code, not the error code - since it is not a generally valid sqlstate. We may still need a place holder for codes though. > add proper SQLState for timeout/cancel > -------------------------------------- > > Key: TEIID-97 > URL: https://issues.jboss.org/browse/TEIID-97 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 7.4.1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Query timeouts/cancel should set the SQLState to 57014 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-97) add proper SQLState for timeout/cancel

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-97?page=com.atlassian.jira.plugin.s... ] Steven Hawkins updated TEIID-97: -------------------------------- Fix Version/s: 7.4.1 (was: 9.x) Affects Version/s: 6.0.0 (was: 9.x) Priority: Optional (was: Trivial) > add proper SQLState for timeout/cancel > -------------------------------------- > > Key: TEIID-97 > URL: https://issues.jboss.org/browse/TEIID-97 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.4.1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Query timeouts/cancel should set the SQLState to 57014 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-59) Oracle timestamp to string and MetaMatrix timestamp to string differ

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-59?page=com.atlassian.jira.plugin.s... ] Steven Hawkins resolved TEIID-59. --------------------------------- Resolution: Won't Fix The docs have been updated with a warning to not rely on exact source conversions. In this case the major format is close enough that the user should workaround by using a method of than exact string comparison. > Oracle timestamp to string and MetaMatrix timestamp to string differ > -------------------------------------------------------------------- > > Key: TEIID-59 > URL: https://issues.jboss.org/browse/TEIID-59 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 9.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 9.x > > > Defect Tracker #24714: Oracle timestamp to string and MetaMatrix timestamp to string differ. Oracle converts timestamps by preserving factional seconds i.e. xxxx.000000000, while the standard timestamp to string will truncate i.e. xxxx.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1620) Fetch keyword not handled

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1620?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1620. ----------------------------------- Assignee: Steven Hawkins Resolution: Done Added support for the offset/fetch clauses. The default representation at this point will still be as a LIMIT clause (this means that in Designer entering a fetch clause will be shown as a limit clause). This required adding OFFSET as a reserved word. > Fetch keyword not handled > ------------------------- > > Key: TEIID-1620 > URL: https://issues.jboss.org/browse/TEIID-1620 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Environment: JBDS 4.0 > Reporter: Joel Tosi > Assignee: Steven Hawkins > Priority: Minor > Fix For: 7.5 > > > Try to limit your query using native SQL construct fetch. While there are other ways to do this inside designer, support the native SQL construct for ease of use by data architects: > select * from SAMPLE_DATABASE fetch first 100 rows only > jBoss Designer error: > select * from SAMPLE_DATABASE fetch first 100 rows only > Remote org.teiid.api.exception.query.QueryParserException: Parsing error: > Encountered "fetch" at line 1, column 36. > Was expecting one of: > <EOF> > "group" ... > "having" ... > "intersect" ... > "limit" ... > "makedep" ... > "makenotdep" ... > "order" ... > "where" ... > "," ... > ";" ... > "union" ... > "except" ... > "option" ... > "cross" ... > "right" ... > "left" ... > "full" ... > "inner" ... > "join" ... > Elapsed Time: 0 hr, 0 min, 0 sec, 0 ms. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-992?page=com.atlassian.jira.plugin.... ] Steven Hawkins commented on TEIID-992: -------------------------------------- You should start with the reference to see the system procedures (settablestats, setcolumnstats) and the developers guide to understand the MetadataRepository interface. As for an end-to-end example, none exists. It is currently up to the user to gather the stats using whatever mechanism they want. > Improve update of source costing statistics > ------------------------------------------- > > Key: TEIID-992 > URL: https://issues.jboss.org/browse/TEIID-992 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Query Engine > Reporter: Marc Shirley > Fix For: 8.0 > > > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-992?page=com.atlassian.jira.plugin.... ] Van Halbert commented on TEIID-992: ----------------------------------- Are there any examples of how all that fits together in order for it to work? > Improve update of source costing statistics > ------------------------------------------- > > Key: TEIID-992 > URL: https://issues.jboss.org/browse/TEIID-992 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Query Engine > Reporter: Marc Shirley > Fix For: 8.0 > > > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-992?page=com.atlassian.jira.plugin.... ] Steven Hawkins commented on TEIID-992: -------------------------------------- As of 7.4, stats are manually updatable/retrievable through system procedures, see the reference. However for updates to be persistent, a MetadataRepository is required. Also there are no gathering routines. An example of what that may look like is on TEIID-245. > Improve update of source costing statistics > ------------------------------------------- > > Key: TEIID-992 > URL: https://issues.jboss.org/browse/TEIID-992 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Query Engine > Reporter: Marc Shirley > Fix For: 8.0 > > > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-992?page=com.atlassian.jira.plugin.... ] Van Halbert commented on TEIID-992: ----------------------------------- What would it take to get the stats retrieved and updated via adminapi? > Improve update of source costing statistics > ------------------------------------------- > > Key: TEIID-992 > URL: https://issues.jboss.org/browse/TEIID-992 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Query Engine > Reporter: Marc Shirley > Fix For: 8.0 > > > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1620) Fetch keyword not handled

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1620?page=com.atlassian.jira.plugin... ] Steven Hawkins moved TEIIDDES-970 to TEIID-1620: ------------------------------------------------ Project: Teiid (was: Teiid Designer) Key: TEIID-1620 (was: TEIIDDES-970) Issue Type: Feature Request (was: Bug) Affects Version/s: (was: 7.2) Component/s: Query Engine (was: Validation) Fix Version/s: 7.5 (was: 7.5) > Fetch keyword not handled > ------------------------- > > Key: TEIID-1620 > URL: https://issues.jboss.org/browse/TEIID-1620 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Environment: JBDS 4.0 > Reporter: Joel Tosi > Priority: Minor > Fix For: 7.5 > > > Try to limit your query using native SQL construct fetch. While there are other ways to do this inside designer, support the native SQL construct for ease of use by data architects: > select * from SAMPLE_DATABASE fetch first 100 rows only > jBoss Designer error: > select * from SAMPLE_DATABASE fetch first 100 rows only > Remote org.teiid.api.exception.query.QueryParserException: Parsing error: > Encountered "fetch" at line 1, column 36. > Was expecting one of: > <EOF> > "group" ... > "having" ... > "intersect" ... > "limit" ... > "makedep" ... > "makenotdep" ... > "order" ... > "where" ... > "," ... > ";" ... > "union" ... > "except" ... > "option" ... > "cross" ... > "right" ... > "left" ... > "full" ... > "inner" ... > "join" ... > Elapsed Time: 0 hr, 0 min, 0 sec, 0 ms. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2011