April 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1328) API request: Programatically modify the VDB

by Mark Addleman (JIRA)

API request: Programatically modify the VDB -------------------------------------------- Key: TEIID-1328 URL: https://jira.jboss.org/browse/TEIID-1328 Project: Teiid Issue Type: Feature Request Components: AdminApi Affects Versions: 7.1 Reporter: Mark Addleman Assignee: Steven Hawkins Priority: Minor I'd like an API to programatically modify the VDB. It would be ideal to modify the VDB using DDL through Teiid. Our primary use case is accessing a dynamic set of datasources through Teiid. When a datasource is added, we would INSERT the appropriate entries into MODEL, PROPERTIES, DATASOURCES tables. Teiid would reread the appropriate metadata from the associated translators. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 12 months

6
35
0 / 0

[JBoss JIRA] Created: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner

by Mark Addleman (JIRA)

API request: rewrite query/command before it reaches the teiid planner ----------------------------------------------------------------------- Key: TEIID-1326 URL: https://jira.jboss.org/browse/TEIID-1326 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1 Reporter: Mark Addleman Assignee: Steven Hawkins I'd like an API to inspect and rewrite a user query/command before it reaches the Teiid planner. The use case is to rewrite the query/command to implement view-like capabilities. For example: SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as: SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t I imagine this API would be similar to the translator API: it would receive a data structure representing the query/command and use a visitor to rewrite the query. As a convenience, it would be nice to have something similar to the SQLConversionVisitor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

6
19
0 / 0

[JBoss JIRA] Created: (TEIID-1540) Add the ability to delegate one shot dependent joins to the translators

by Steven Hawkins (JIRA)

Add the ability to delegate one shot dependent joins to the translators ----------------------------------------------------------------------- Key: TEIID-1540 URL: https://issues.jboss.org/browse/TEIID-1540 Project: Teiid Issue Type: Sub-task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 Using a memory safe iterator, like with bulk handling, we should be able to push dependent joins to the translator to perform specialized source specific one-shot join handling. With the other dependent join improvements this should hopefully be needed only in the most extreme cases. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-1352) Produce Admin API jar containing only Interfaces.

by John Doyle (JIRA)

Produce Admin API jar containing only Interfaces. ------------------------------------------------- Key: TEIID-1352 URL: https://jira.jboss.org/browse/TEIID-1352 Project: Teiid Issue Type: Feature Request Components: AdminApi Reporter: John Doyle Assignee: Steven Hawkins TEIIDDES-175 requires the creation of a target runtime for Teiid so that the tooling can be further abstracted from changes in Teiid. In order to accomplish this the tooling requires an Admin API jar containing only interfaces. The Designer code that depends upon the Admin API could be compiled with this jar, and the plug-in defining the target runtime would load the implementation of the Admin API at runtime. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

7
11
0 / 0

[JBoss JIRA] Created: (TEIID-1268) Add support for using the case insensitive metadata

by Steven Hawkins (JIRA)

Add support for using the case insensitive metadata --------------------------------------------------- Key: TEIID-1268 URL: https://jira.jboss.org/browse/TEIID-1268 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 8.0 We currently capture whether the source is case sensitive and thus have a place holder on both physical and virtual models, but we do not use this information in performing comparisons in teiid. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1465) Join between char and varchar

by Claudio Venturini (JIRA)

Join between char and varchar ----------------------------- Key: TEIID-1465 URL: https://issues.jboss.org/browse/TEIID-1465 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 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 Joins between char and varchar fields fail. Suppose to have a table T1 with a field A, declared as char(10), and a table T2 with a field B, declared as varchar(10). Suppose that the two tables have the following data. *T1*: ||A|| |ML0001| *T2*: ||B|| |ML0001| When performing a INNER JOIN with the condition {{T1.A = T2.B}} the result set is empty, even if the two record match correctly. This happens when the two base tables refer to two different sources, because if they are in the same source Teiid pushes the join to the source, which computes it correctly. I think the problem is in the comparison of the two strings. I have the table T1 in SQL Server 2000, and the table T2 in MySQL 5.1. If one asks SQL Server to convert the string to bytes, the result is {{0x4D4C3030303120202020}}, because the string is filled with (invisible) blanks in order to reach the limit of 10 characters. Note that if one asks for the length of that string, SQL Server states (correctly) that it is 6 characters. The string in MySQL is a VARCHAR(10), so its conversion to binary is {{0x4D4C30303031}}. I think that Teiid compares the two binary strings in their entire length. That comparison fails, and no match is found. The problem remains even if the table T1 is placed in MySQL, and T2 in SQL Server (the opposite situation). I also verified that the problem exists either when querying the source models or view models built over them. *Workaround:* A workaround exists but it is too complex (IMHO). I haven't tested it with many records, but I think it will slow down performances considerably. It consists in casting the string from char to varchar, and then trimming it (with RTRIM() and LTRIM() because SQL Server doesn't support TRIM()). So the join condition is: {noformat} RTRIM(LTRIM(CAST(T1.A AS VARCHAR))) = T2.B {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
8
0 / 0

[JBoss JIRA] Created: (TEIID-1528) ruleimplementjoin strategy may generate an order by that does not use a relevant index

by Steven Hawkins (JIRA)

ruleimplementjoin strategy may generate an order by that does not use a relevant index -------------------------------------------------------------------------------------- Key: TEIID-1528 URL: https://issues.jboss.org/browse/TEIID-1528 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins If a table is given additional join criteria not covered by an index or if a composite key is being used ruleimplementjoinstrategy may - either add an item not covered by the index to the order by or not use the proper order of the index columns. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
6
0 / 0

[JBoss JIRA] Created: (TEIID-1448) XMLTABLE processing should support streaming when possible

by Steven Hawkins (JIRA)

XMLTABLE processing should support streaming when possible ---------------------------------------------------------- Key: TEIID-1448 URL: https://issues.jboss.org/browse/TEIID-1448 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Just like the old xml/relational processing if the xpaths/xquery used is sufficiently restrictive the xml can be processed in a streaming fashion - where independent siblings are processed independently without loading the rest of the document. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIID-1507) Cache invalidation

by Steven Hawkins (JIRA)

Cache invalidation ------------------ Key: TEIID-1507 URL: https://issues.jboss.org/browse/TEIID-1507 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins We should provide an interface and internally react to events of updates to vdbname/version/table/row and purge resultset cache and possibly materialization. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-1536) Local connections should use calling thread

by Steven Hawkins (JIRA)

Local connections should use calling thread ------------------------------------------- Key: TEIID-1536 URL: https://issues.jboss.org/browse/TEIID-1536 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 locsl connections block on jdbc operations, but mostly do not use the calling thread in the engine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2011