May 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2482) Allow the use of the enhanced join for left outer joins

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2482?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2482: --------------------------------- Fix Version/s: 7.7.7 > Allow the use of the enhanced join for left outer joins > ------------------------------------------------------- > > Key: TEIID-2482 > URL: https://issues.jboss.org/browse/TEIID-2482 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4, 7.7.7 > > > Left equi outer joins are currently only implemented using the full sort merge join and would benefit from using the enhanced merge when the inner side is relatively small. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2491) ODBC ScriptReader workarounds do not handle EOF

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2491?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2491: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=961071 > ODBC ScriptReader workarounds do not handle EOF > ----------------------------------------------- > > Key: TEIID-2491 > URL: https://issues.jboss.org/browse/TEIID-2491 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > Issuing a query such as select 'foo'::bar > will result in an error since the workaround to drop the ::bar appends the EOF to the sql text. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2478) incomplete with pushdown

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2478?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2478: --------------------------------- Fix Version/s: 7.7.7 > incomplete with pushdown > ------------------------ > > Key: TEIID-2478 > URL: https://issues.jboss.org/browse/TEIID-2478 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4, 7.7.7 > > > If all the with clauses are not fully pushed, but is still pushable, the resulting query plan will contain incomplete references to the clauses. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2460) Weird behavior when Max buffer space restriction is hit

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2460?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2460: --------------------------------- Fix Version/s: 7.7.7 > Weird behavior when Max buffer space restriction is hit > -------------------------------------------------------- > > Key: TEIID-2460 > URL: https://issues.jboss.org/browse/TEIID-2460 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7.6 > Reporter: Filip Nguyen > Assignee: Steven Hawkins > Fix For: 8.4, 7.7.7 > > Attachments: teiid-jboss-beans.xml > > > I was trying to restrict the disk space used by buffer manager (see steps to reproduce for my methodology). When the disk limit is hit, it really tries to stop the query, but doesn't succeed immediately. > There is a big amount of exceptions [1] for relatively long period of time (minutes for big files), until it fails eventually with [2]. The error [2] is also given back to the JDBC client. > Problem is that after the query fails in this fashion, the whole buffer disk space is still occupied and any new query, that needs even small (acceptable) buffer disk space, fails. > Only way that I have found to make the buffer space usable again is to restart the server. > [1] Error transferring block to storage 149742 > java.io.IOException: Max buffer space of 31,457,280 bytes has been exceed. The current operation will be aborted. > [2] org.teiid.jdbc.TeiidSQLException: Batch not found in storage 50937 -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2363) proactive buffering not occurring for the inner side of an outer join on "MERGE JOIN (SORT/ALREADY_SORTED)"

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2363?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2363: --------------------------------- Fix Version/s: 7.7.7 (was: 7.7.6) > proactive buffering not occurring for the inner side of an outer join on "MERGE JOIN (SORT/ALREADY_SORTED)" > ----------------------------------------------------------------------------------------------------------- > > Key: TEIID-2363 > URL: https://issues.jboss.org/browse/TEIID-2363 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.7.2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.4, 7.7.7 > > > The issue here is this is an outer join and the inner side (the already sorted side) will be buffered regardless. Current logic does not catch blocked exceptions from one side and pro-actively buffer the other - rather we are serially performing the sort and then continue with the loading of the inner side > For inner joins there is a clear trade-off between execution speed and buffering so this behavior may have to be hint or config driven for non-dependent non-outer joins. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2455) Cannot execute SQL query using SQL function in SORT clause via view model

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2455?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2455: --------------------------------- Fix Version/s: 7.7.7 > Cannot execute SQL query using SQL function in SORT clause via view model > ------------------------------------------------------------------------- > > Key: TEIID-2455 > URL: https://issues.jboss.org/browse/TEIID-2455 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7.4 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.4, 7.7.7 > > > If SQL query is contained using SQL function in SORT clause, the query cannot execute via view model. > ex) SELECT C1 FROM TEST_TABLE_VW order by CAST(C3 AS integer) > Version-Release number of selected component (if applicable): > EDS 5.3.1 -- 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

12 years, 10 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 Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2361?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2361: --------------------------------- Fix Version/s: 7.7.7 > 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, 7.7.7 > > > 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2502) org.teiid.net.socket.SingleInstanceCommunicationException

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2502?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2502: --------------------------------------- > It seems that oracle.sql.struts is serializable. It is marked as serializable, but carries the connection object as a member, and thus fails in the simplistic case of just trying to write the struct instance out. As the doc covers and what I'm referring to above is that there are other options for retrieving the information contained by the struct - namely the getAttributes method that is not oracle specific. > It should be possible to map also to java.sql.structs and maybe this could solve? I was hoping that retrieval as blob or string may have been possible, but as your next comment indicates that did not work. > Can be a problem the fact that the designer mappet to object (is there a mapping to structs?). There is no built-in handling for structs either in Teiid or Teiid Designer. > Let me know if there is a plan for solving this ... but the oracle spatial connector that should have been merged with the standard one did not address this? The oracle spatial logic simply covered adding function hooks for common spatial options, but generally represented a spatial type as object and just expected to return simple scalar and not spatial type results. TEIID-2384 is the issue to generally add support for spatial types. Like I said above the quickest fix would be to extend the OracleExecutionFactory and when retrieving objects do an instance check for STRUCT and instead return a SerialStruct, which will be fully serializable. Another user directed fix would be to add a udf that would do the same - or convert to whatever representation that you want. Otherwise you'll have to wait for the built-in fix, which will likely be just to use the SerialStruct approach. We just need to make sure that this won't conflict with any later handling of structs, what sources need overrides - but we aren't likely to add full type (in Designer or DDL) handling yet. > org.teiid.net.socket.SingleInstanceCommunicationException > --------------------------------------------------------- > > Key: TEIID-2502 > URL: https://issues.jboss.org/browse/TEIID-2502 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.2 > Environment: centos 6.3 > Reporter: luca gioppo > Assignee: Steven Hawkins > Priority: Critical > > 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2502) org.teiid.net.socket.SingleInstanceCommunicationException

by luca gioppo (JIRA)

[ https://issues.jboss.org/browse/TEIID-2502?page=com.atlassian.jira.plugin... ] luca gioppo commented on TEIID-2502: ------------------------------------ No the designer just allows for object that is consideres a base64binary, but I believe that cannot be matched with the struct datatype. So no luck with that. Let me know if there is a plan for solving this ... but the oracle spatial connector that should have been merged with the standard one did not address this? > org.teiid.net.socket.SingleInstanceCommunicationException > --------------------------------------------------------- > > Key: TEIID-2502 > URL: https://issues.jboss.org/browse/TEIID-2502 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.2 > Environment: centos 6.3 > Reporter: luca gioppo > Assignee: Steven Hawkins > Priority: Critical > > 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2502) org.teiid.net.socket.SingleInstanceCommunicationException

by luca gioppo (JIRA)

[ https://issues.jboss.org/browse/TEIID-2502?page=com.atlassian.jira.plugin... ] luca gioppo commented on TEIID-2502: ------------------------------------ It seems that oracle.sql.struts is serializable. This link can perhaps help: http://docs.oracle.com/cd/B13789_01/java.101/b10979/oraoot.htm It should be possible to map also to java.sql.structs and maybe this could solve? Can be a problem the fact that the designer mappet to object (is there a mapping to structs?). I'll give it a try (if the structs mapping exists). Hope this can help. Luca > org.teiid.net.socket.SingleInstanceCommunicationException > --------------------------------------------------------- > > Key: TEIID-2502 > URL: https://issues.jboss.org/browse/TEIID-2502 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.2 > Environment: centos 6.3 > Reporter: luca gioppo > Assignee: Steven Hawkins > Priority: Critical > > 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

12 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2013