June 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2556) Dependent join pushdown with array type incorrect

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2556?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2556. ----------------------------------- Resolution: Done corrected the language bridge factory logic to be consistent with the other array handling and created an array of parameters. > Dependent join pushdown with array type incorrect > ------------------------------------------------- > > Key: TEIID-2556 > URL: https://issues.jboss.org/browse/TEIID-2556 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > When pushing a dependent join with source array type support, the resulting comparison uses a single parameter with a value index of -1. It should instead use an array of parameters with the correct indexes. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2557) Provide support for Composite Foreign Keys in MongoDB

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2557: ----------------------------------- Summary: Provide support for Composite Foreign Keys in MongoDB Key: TEIID-2557 URL: https://issues.jboss.org/browse/TEIID-2557 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.4 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.4.1 TEIID-2529 provided support for PK, but missed the FKs that have multiple keys, this need to be fixed -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2556) Dependent join pushdown with array type incorrect

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2556: ------------------------------------- Summary: Dependent join pushdown with array type incorrect Key: TEIID-2556 URL: https://issues.jboss.org/browse/TEIID-2556 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.4.1, 8.5 When pushing a dependent join with source array type support, the resulting comparison uses a single parameter with a value index of -1. It should instead use an array of parameters with the correct indexes. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2555) Support pushdown of entire dependent joins

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2555: ------------------------------------- Summary: Support pushdown of entire dependent joins Key: TEIID-2555 URL: https://issues.jboss.org/browse/TEIID-2555 Project: Teiid Issue Type: Sub-task Components: Connector API, Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.5 If the data volume is not too large then in many circumstances pushing down the entire independent side of the join to perform the entire join at the source can enhance performance. This would likely be built upon TEIID-2249 to make use of a make dep hint option. It would also likely be an expansion of the common table pushdown logic - but will require more extensive planning changes as the default logic is geared toward only the equi-join columns. It has also been requested that the default preference for pushdown be based upon the estimated data width. There is an issue with the form of the plan as with the existing logic it would be nearly impossible to back out of the decision to perform the full pushdown (which is why a hint is initially preferable). Marking the initial target at 8.5, but will likely slip. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2249) Enable the use of temporary tables for those data sources that support them instead of IN criteria for EDS

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2249?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2249: ---------------------------------- Fix Version/s: 8.5 (was: 8.4.1) Based upon the size of even the initial hinting/capabilities changes I will initially target the changes at 8.5. We can then decide to back port if needed. > Enable the use of temporary tables for those data sources that support them instead of IN criteria for EDS > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-2249 > URL: https://issues.jboss.org/browse/TEIID-2249 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.5 > > > Our proposal is to allow for the more efficient use of large ad-hoc result-sets by rather than creating a long 'IN' list, inserting them in to a temporary table - for example a # table in Sybase and SQL Server - and then generating an SQL join to that instead. > One of the difference to materialized views (or at least my understanding), is that this work happens at a data-source rather than within the Teiid server. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2502) Oracle Struct Serialization Error

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2502?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2502. ----------------------------------- Resolution: Done Added the structretrieval translator property. It can be one of OBJECT (default), COPY, ARRAY. In the thread linked to this issue, COPY mode would address the serialization error. ARRAY mode can be used to retrieve a value that can be utilized by the Teiid array logic (array_get, arraytable, etc.). When additional handling is added for struct/array types in the engine we can revisit this support. > Oracle Struct Serialization Error > --------------------------------- > > Key: TEIID-2502 > URL: https://issues.jboss.org/browse/TEIID-2502 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.2 > Environment: centos 6.3 > Reporter: luca gioppo > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > Attachments: ora.patch > > > I'm issuing a query (a simple select * from table) on a VDB's table that contains a geometric column from oracle spatial. > I'm getting the following error in SquirrelSQL > Error: org.teiid.net.socket.SingleInstanceCommunicationException > SQLState: 08S01 > ErrorCode: 0 > Afterwards the connection is broken and I cannot access any other table and have to reconnect since I get: > Error: Error Code:TEIID20013 Message:Error Code:TEIID20013 Message:java.net.SocketException: Socket closed > SQLState: TEIID20013 > ErrorCode: 0 > I'm trying to access a SDO table and a geometry type column, but hoped that TEIID could read it as a BLOB without caring about the real type. > Probably it doesn't like it too much. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2249) Enable the use of temporary tables for those data sources that support them instead of IN criteria for EDS

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2249?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2249: --------------------------------------- Pushdown of the entire join may be done as a variation of common table pushdown, where a tuplesource is provided to define a common table (other details such as index creation, etc. TBD). That would likely follow in 8.5 or later. For 8.4.1 I am thinking that we'll add an additional configurable translator property along the lines of "dependentJoinPushdownMinimum". This would likely be an integer indicating that dependent joins exceeding that number of distinct independent values should be pushed down. Presumably a user would set it to a value that would be over what would be performant with several in pushdown queries (even when executed in parallel) such as 100000 independent values. Then the option makedep and positional makedep hints would be altered to all for the additional specification of dependent join options - option makedep tbl (min:50000 join) Here min would override the translator property and join would indicate that the whole join would be pushed down. > Enable the use of temporary tables for those data sources that support them instead of IN criteria for EDS > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-2249 > URL: https://issues.jboss.org/browse/TEIID-2249 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.4.1 > > > Our proposal is to allow for the more efficient use of large ad-hoc result-sets by rather than creating a long 'IN' list, inserting them in to a temporary table - for example a # table in Sybase and SQL Server - and then generating an SQL join to that instead. > One of the difference to materialized views (or at least my understanding), is that this work happens at a data-source rather than within the Teiid server. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2384) Managing Spatial Data Types

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2384?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2384: ---------------------------------- Fix Version/s: 8.5 Building on TEIID-2502 we should offer more support for the spatial type and at the least importing/defining additional common spatial functions for oracle/pg/etc. > Managing Spatial Data Types > --------------------------- > > Key: TEIID-2384 > URL: https://issues.jboss.org/browse/TEIID-2384 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.2 > Reporter: luca gioppo > Assignee: Steven Hawkins > Labels: spatial, types > Fix For: 8.5 > > > It would be useful to be able to consume data from spatial database exposing the VDB as a spatial database to other application (imagine geoserver). > TEIID could be strategic for merging georeferenced data and make it available to those systems. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2502) Oracle Struct Serialization Error

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2502?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2502: ---------------------------------- Fix Version/s: 8.4.1 > Oracle Struct Serialization Error > --------------------------------- > > Key: TEIID-2502 > URL: https://issues.jboss.org/browse/TEIID-2502 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.2 > Environment: centos 6.3 > Reporter: luca gioppo > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > Attachments: ora.patch > > > I'm issuing a query (a simple select * from table) on a VDB's table that contains a geometric column from oracle spatial. > I'm getting the following error in SquirrelSQL > Error: org.teiid.net.socket.SingleInstanceCommunicationException > SQLState: 08S01 > ErrorCode: 0 > Afterwards the connection is broken and I cannot access any other table and have to reconnect since I get: > Error: Error Code:TEIID20013 Message:Error Code:TEIID20013 Message:java.net.SocketException: Socket closed > SQLState: TEIID20013 > ErrorCode: 0 > I'm trying to access a SDO table and a geometry type column, but hoped that TEIID could read it as a BLOB without caring about the real type. > Probably it doesn't like it too much. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2249) Enable the use of temporary tables for those data sources that support them instead of IN criteria for EDS

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIID-2249?page=com.atlassian.jira.plugin... ] Debbie Steigner commented on TEIID-2249: ---------------------------------------- Response to Steve from Nelson : Please pass this information to Steven. Below is exactly how I would expect it to work. The reason is we can do aggregation at source instead of in Teiid to reduce the volume of data being transferred across the wire and performance reason too. "The other possibility is that he means the entirety of the independent/driving side of the join would be shipped to form the temporary table such that the complete results are read by Teiid instead of a secondary in-Teiid join being performed." Nelson > Enable the use of temporary tables for those data sources that support them instead of IN criteria for EDS > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-2249 > URL: https://issues.jboss.org/browse/TEIID-2249 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.4.1 > > > Our proposal is to allow for the more efficient use of large ad-hoc result-sets by rather than creating a long 'IN' list, inserting them in to a temporary table - for example a # table in Sybase and SQL Server - and then generating an SQL join to that instead. > One of the difference to materialized views (or at least my understanding), is that this work happens at a data-source rather than within the Teiid server. -- 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, 7 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 2013