February 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-784) Enhance distinct set op processing

by Steven Hawkins (JIRA)

Enhance distinct set op processing ---------------------------------- Key: TEIID-784 URL: https://jira.jboss.org/jira/browse/TEIID-784 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.3.0 The sort operation should be able to pushed for each set op child (distinct is already eligible for pushing, but typically won't be because there's no order by). Also for union the sorted children should be fed directly into the second phase of sorting. All of this relies on the connector guaranteeing null ordering (TEIID-715 should be repurposed to cover the language enhancement of nulls first|last) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Updated: (TEIID-303) Remove the LanguageBridgeFactory

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-303?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-303: --------------------------------- Fix Version/s: 9.0 (was: 8.0) pushing to 9.0 > Remove the LanguageBridgeFactory > -------------------------------- > > Key: TEIID-303 > URL: https://issues.jboss.org/browse/TEIID-303 > Project: Teiid > Issue Type: Task > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > Defect Tracker #25061: The language objects at the data layer are redundent with the language objects used in commands. The LanguageBridgeFactory can be removed in favor of simply cloning and issuing a command. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-321) Refactor symbol language objects

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-321?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-321: --------------------------------- Fix Version/s: 9.0 (was: 8.0) pushing to 9.0 > Refactor symbol language objects > -------------------------------- > > Key: TEIID-321 > URL: https://issues.jboss.org/browse/TEIID-321 > Project: Teiid > Issue Type: Task > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Defect Tracker #25035: The current structuring of Symbol objects is confusing and makes planning more difficult than necessary. Changes that should be made: > AggregateSymbol should become AggregateFunction (which should not inherit from Function) and not be a Symbol. > SingleElementSymbol, ExpressionSymbol, and AliasSymbol should be merged to a single class DerivedSymbol > DerivedSymbol and MultipleElementSymbol should implement SelectSymbol (as an interface rather than base class) and SelectSymbol should provide a method for getting the projected symbols. > ElementSymbol should not directly be a DerivedSymbol. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-226) Cacheing translated commands would improve connector performance

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-226?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-226: --------------------------------- Fix Version/s: 9.0 (was: 8.0) pushing to 9.0 > Cacheing translated commands would improve connector performance > ---------------------------------------------------------------- > > Key: TEIID-226 > URL: https://issues.jboss.org/browse/TEIID-226 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 9.0 > > > Defect Tracker #16722: AD 2/17/05 - Command translation in connector - approx. half the time taken to create an Execution object is spent in command translation. If there was a way to cache the translated command, then we could eliminate that step for subsequent requests. > Alex 2/17/05 - The problem is that the connector can be used with different vdbs, so the translation may be different even for the same query. Still seems do-able [...]. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1035) Replace Existing XML Document Functionality with other JBoss Technologies

by Ted Jones (JIRA)

Replace Existing XML Document Functionality with other JBoss Technologies ------------------------------------------------------------------------- Key: TEIID-1035 URL: https://jira.jboss.org/jira/browse/TEIID-1035 Project: Teiid Issue Type: Task Affects Versions: 7.0 Reporter: Ted Jones Assignee: Steven Hawkins Fix For: 8.0 The current XML Document homegrown technologies in the Teiid Designer with existing JBoss technologies. The following use cases should be satisfied: 1. Start with an XML Schema to build a Document that can be filled with relational, heterogeneous data and "shipped around" 2. Given an XML document/message definition, submit a query on the document with criteria defined within the document structure 3. Send an input document, produce and output document -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIID-587) Better pushdown support for exotic joins

by Steven Hawkins (JIRA)

Better pushdown support for exotic joins ---------------------------------------- Key: TEIID-587 URL: https://jira.jboss.org/jira/browse/TEIID-587 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 Our optimizations get in the way of Salesforce pushdown. Specifically rewriting like when possible to = and converting outer joins to inner joins. In both cases we would need to not perform the optimization in the first place or convert into an acceptable form prior to pushdown. The next is that salesforce, while requiring key criteria also allows other criteria in the left outer join on clause (which would be the same as having criteria on the nested relationship query in the salesforce query). With the capabilities as currently defined this would cause the query to not be pushed down. We should consider adding a relational supported join criteria type that requires key criteria but allows for outside criteria. Also we should treat the lack of inner join support to mean that criteria on the inner side of an outer join cannot be pushed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
4
0 / 0

[JBoss JIRA] Resolved: (TEIID-99) Stored procedures should work in multisource connector binding scenarios

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-99?page=com.atlassian.jira.plugin.s... ] Steven Hawkins resolved TEIID-99. --------------------------------- Labels: multisource (was: ) Fix Version/s: 7.4 (was: 8.0) Resolution: Done Updated multisource planning to allow for an explicit multisource procedure parameter source_name. Added more validation to both the procedure and insert cases. Corrected the handling of insert/update when no sources match. Also add docs of multisource in general and the procedure scenario in particular > Stored procedures should work in multisource connector binding scenarios > ------------------------------------------------------------------------ > > Key: TEIID-99 > URL: https://issues.jboss.org/browse/TEIID-99 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Labels: multisource > Fix For: 7.4 > > > Defect Tracker #24614: Stored procedures should work in multisource connector binding scenarios by adding another input parameter named SOURCE_NAME -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1459) Wrong count(*) result when joining data from two models

by Van Halbert (JIRA)

Wrong count(*) result when joining data from two models ------------------------------------------------------- Key: TEIID-1459 URL: https://issues.jboss.org/browse/TEIID-1459 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.2, 7.3 Environment: Teiid 7.3 deployed on Jboss AS 5.1.0 GA running on Ubuntu Server 10.04 LTS, MySQL 5.1.51 running on the same machine as JBoss, SQL Server 2000 Standard SP4 running on Windows Server 2003 Reporter: Claudio Venturini Assignee: Steven Hawkins Fix For: 7.4 count(\*) gets a wrong result when is performed in a query which joins two tables coming from two different models. The first (named "sqlsrv") is a source model for a table stored in SQL Server 2000. The second (named "mysql") is a source model for a table stored in MySQl 5.1. The query performs an inner join on the column "product_id", which is shared by the two tables. All records match correctly, so there should be no difference in using an inner join instead of other join types. The query is the following: {noformat} SELECT invoice, invoice_date, code, sum(quantity) AS s, avg(price) AS av, count(*) AS dim FROM sqlsrv.test2.dbo.sales SL INNER JOIN mysql.test.product_code PC ON SL.product_id = PC.product_id GROUP BY invoice_date, invoice, code ORDER BY invoice_date ASC, invoice ASC, code ASC {noformat} The result of count(\*) is 1 for all records, while for some of them it should be 2, as there are duplicate records in the sales table, which are grouped by the GROUP BY clause. Note that the problem exists only with the inner join. Left, right and outer joins work well, even if the set of records that they produce is the same as that produced by the inner join. I noticed the problem in Teiid 7.2. Tonight I upgraded to 7.3, but the problem is still there. If the data are all in the same DB, the query works as expected. It is not significant in which of the two DB each table resides. I think it is neither a problem of the SQL Server connector, nor of the MySQL connector. The data are the following: *product_code*: ||code||category||product_id|| |1|1|125| |2|1|127| |3|1|123| |4|1|121| |5|1|126| |6|1|124| |7|1|122| *sales*: ||invoice||invoice_date||product_id||quantity||price|| |009831|2009-08-15 00:00:00|125|350|1.070261| |009831|2009-08-15 00:00:00|124|960|1.070261| |009843|2009-08-15 00:00:00|121|648|1.515264| |009843|2009-08-15 00:00:00|126|145|2.763902| |009843|2009-08-15 00:00:00|126|25|2.407148| |009855|2009-08-15 00:00:00|122|768|1.122835| |009855|2009-08-15 00:00:00|123|540|1.158511| |009855|2009-08-15 00:00:00|125|480|1.070261| |009857|2009-08-15 00:00:00|122|440|1.498365| |009857|2009-08-15 00:00:00|126|115|2.585525| |009866|2009-08-15 00:00:00|122|736|1.498365| |009866|2009-08-15 00:00:00|123|558|1.391339| |009866|2009-08-15 00:00:00|125|378|1.336887| |009866|2009-08-15 00:00:00|127|510|1.605391| |009866|2009-08-15 00:00:00|126|435|2.585525| |009847|2009-08-15 00:00:00|126|55|2.763902| |009847|2009-08-15 00:00:00|126|5|2.407148| |009847|2009-08-15 00:00:00|121|240|1.872018| The result of the above query is: ||invoice||invoice_date||code||s||av||dim|| |009831|2009-08-15 00:00:00|1|350.0|1.070261|1| |009831|2009-08-15 00:00:00|6|960.0|1.070261|1| |009843|2009-08-15 00:00:00|4|648.0|1.515264|1| |009843|2009-08-15 00:00:00|5|170.0|2.585525|1| |009847|2009-08-15 00:00:00|4|240.0|1.872018|1| |009847|2009-08-15 00:00:00|5|60.0|2.585525|1| |009855|2009-08-15 00:00:00|1|480.0|1.070261|1| |009855|2009-08-15 00:00:00|3|540.0|1.158511|1| |009855|2009-08-15 00:00:00|7|768.0|1.122835|1| |009857|2009-08-15 00:00:00|5|115.0|2.585525|1| |009857|2009-08-15 00:00:00|7|440.0|1.498365|1| |009866|2009-08-15 00:00:00|1|378.0|1.336887|1| |009866|2009-08-15 00:00:00|2|510.0|1.605391|1| |009866|2009-08-15 00:00:00|3|558.0|1.391339|1| |009866|2009-08-15 00:00:00|5|435.0|2.585525|1| |009866|2009-08-15 00:00:00|7|736.0|1.498365|1| As you can see, count(\*) (the "dim" column) always returns 1, even if it should return 2 for the product with id 126 in invoices 009843 and 009847. If needed, I can provide you the two source models, and a dump of the two DBs. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 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 2011