April 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3436) Add array type support to the odata translator

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3436: ------------------------------------- Summary: Add array type support to the odata translator Key: TEIID-3436 URL: https://issues.jboss.org/browse/TEIID-3436 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Reporter: Steven Hawkins Assignee: Steven Hawkins Arrays of basic types in odata responses should be convertible into a runtime array type. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3426) Salesforce importer does not set cardinalities

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3426?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3426: ---------------------------------- Fix Version/s: 8.11 > Salesforce importer does not set cardinalities > ---------------------------------------------- > > Key: TEIID-3426 > URL: https://issues.jboss.org/browse/TEIID-3426 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Reporter: Burak Serdar > Assignee: Steven Hawkins > Fix For: 8.11 > > > The salesforce importer does not set cardinalities for salesforce objects it imports. That is causing problems with joins involving more than two tables, and when there are no criteria on a large table. If the large table is joined later, it retrieves all the rows of that table and joins them with the result of the previous joins. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3434) Ability to enable/disable caching by table and/or source

by Burak Serdar (JIRA)

[ https://issues.jboss.org/browse/TEIID-3434?page=com.atlassian.jira.plugin... ] Burak Serdar updated TEIID-3434: -------------------------------- Updates are external, and they come through different apps, so there is no way to notify changes. It would really help to be able to set a ttl at the table and source level. Some tables/sources keep summarized data that is updated once or twice a day. Some other tables/sources have real-time data, and caching is not desired for those. ----- Original Message ----- > Ability to enable/disable caching by table and/or source > -------------------------------------------------------- > > Key: TEIID-3434 > URL: https://issues.jboss.org/browse/TEIID-3434 > Project: Teiid > Issue Type: Feature Request > Reporter: Burak Serdar > Assignee: Steven Hawkins > > We need to be able to enable/disable caching by table and/or source. Some of our tables have real-time data, and we do not want to cache those, and some other tables can use cached data. It is not sufficient to use SQL options to turn caching on or off, because we're using 3rd party tools, and we don't have control over the SQL they generate. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3435) IllegalStateException closing connection

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3435?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3435: ---------------------------------- Summary: IllegalStateException closing connection (was: XML subquery plans being closed twice) Description: Another thing from the log are what appear to be exceptions related to close calls: {code} 10:30:27,074 INFO [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (http-localhost/127.0.0.1:8080-1) IJ000311: Throwable from unregister connection: java.lang.IllegalStateException: Trying to return an unknown connection2! org.jboss.jca.adapters.jdbc.jdk6.WrappedConnectionJDK6@b036577 at org.jboss.jca.core.connectionmanager.ccm.CachedConnectionManagerImpl.unregisterConnection(CachedConnectionManagerImpl.java:347) at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.connectionClosed(TxConnectionListener.java:371) at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:574) at org.jboss.jca.adapters.jdbc.WrappedConnection.close(WrappedConnection.java:265) at org.teiid.translator.jdbc.JDBCExecutionFactory.closeConnection(JDBCExecutionFactory.java:287) at org.teiid.translator.jdbc.JDBCExecutionFactory.closeConnection(JDBCExecutionFactory.java:51) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.close(ConnectorWorkItem.java:226) [teiid-engine-8.4.2-redhat-1.jar:8.4.2-redhat-1] {code} It looks like it's only happening for the XML subplans. We explicitly prevent close from being called multiple times on connector work item. was: Another thing from the log are what appear to be exceptions related to double close calls: {code} 10:30:27,074 INFO [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (http-localhost/127.0.0.1:8080-1) IJ000311: Throwable from unregister connection: java.lang.IllegalStateException: Trying to return an unknown connection2! org.jboss.jca.adapters.jdbc.jdk6.WrappedConnectionJDK6@b036577 at org.jboss.jca.core.connectionmanager.ccm.CachedConnectionManagerImpl.unregisterConnection(CachedConnectionManagerImpl.java:347) at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.connectionClosed(TxConnectionListener.java:371) at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:574) at org.jboss.jca.adapters.jdbc.WrappedConnection.close(WrappedConnection.java:265) at org.teiid.translator.jdbc.JDBCExecutionFactory.closeConnection(JDBCExecutionFactory.java:287) at org.teiid.translator.jdbc.JDBCExecutionFactory.closeConnection(JDBCExecutionFactory.java:51) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.close(ConnectorWorkItem.java:226) [teiid-engine-8.4.2-redhat-1.jar:8.4.2-redhat-1] {code} It looks like it's only happening for the XML subplans. But it seems odd as we explicitly prevent close from being called multiple times on connector work item. Changed the issue text as it does not appear to be about double closing. See also http://stackoverflow.com/questions/8785798/what-is-the-cause-of-this-erro... > IllegalStateException closing connection > ---------------------------------------- > > Key: TEIID-3435 > URL: https://issues.jboss.org/browse/TEIID-3435 > Project: Teiid > Issue Type: Quality Risk > Affects Versions: 8.7 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > > Another thing from the log are what appear to be exceptions related to close calls: > {code} > 10:30:27,074 INFO > [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] > (http-localhost/127.0.0.1:8080-1) IJ000311: Throwable from unregister > connection: java.lang.IllegalStateException: Trying to return an unknown connection2! org.jboss.jca.adapters.jdbc.jdk6.WrappedConnectionJDK6@b036577 > at > org.jboss.jca.core.connectionmanager.ccm.CachedConnectionManagerImpl.unregisterConnection(CachedConnectionManagerImpl.java:347) > at > org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.connectionClosed(TxConnectionListener.java:371) > at > org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:574) > at > org.jboss.jca.adapters.jdbc.WrappedConnection.close(WrappedConnection.java:265) > at > org.teiid.translator.jdbc.JDBCExecutionFactory.closeConnection(JDBCExecutionFactory.java:287) > at > org.teiid.translator.jdbc.JDBCExecutionFactory.closeConnection(JDBCExecutionFactory.java:51) > at > org.teiid.dqp.internal.datamgr.ConnectorWorkItem.close(ConnectorWorkItem.java:226) > [teiid-engine-8.4.2-redhat-1.jar:8.4.2-redhat-1] > {code} > > It looks like it's only happening for the XML subplans. We explicitly prevent close from being called multiple times on connector work item. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3434) Ability to enable/disable caching by table and/or source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3434?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3434: --------------------------------------- So you are enabling result set caching then by a connection property? We do track result set cache entries down to a table level. If the source updates are through teiid, then the result set cache is already sensitive to those changes. If the changes are external, then either you could look into notifying us of the change events or as an enhancement it seems like what you are looking for is extension metadata on the table to specify the ttl in the cache. Individually enabling materialization can work as well. > Ability to enable/disable caching by table and/or source > -------------------------------------------------------- > > Key: TEIID-3434 > URL: https://issues.jboss.org/browse/TEIID-3434 > Project: Teiid > Issue Type: Feature Request > Reporter: Burak Serdar > Assignee: Steven Hawkins > > We need to be able to enable/disable caching by table and/or source. Some of our tables have real-time data, and we do not want to cache those, and some other tables can use cached data. It is not sufficient to use SQL options to turn caching on or off, because we're using 3rd party tools, and we don't have control over the SQL they generate. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3435) XML subquery plans being closed twice

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3435: ----------------------------------- Summary: XML subquery plans being closed twice Key: TEIID-3435 URL: https://issues.jboss.org/browse/TEIID-3435 Project: Teiid Issue Type: Quality Risk Affects Versions: 8.7 Reporter: Ramesh Reddy Assignee: Steven Hawkins Another thing from the log are what appear to be exceptions related to double close calls: {code} 10:30:27,074 INFO [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (http-localhost/127.0.0.1:8080-1) IJ000311: Throwable from unregister connection: java.lang.IllegalStateException: Trying to return an unknown connection2! org.jboss.jca.adapters.jdbc.jdk6.WrappedConnectionJDK6@b036577 at org.jboss.jca.core.connectionmanager.ccm.CachedConnectionManagerImpl.unregisterConnection(CachedConnectionManagerImpl.java:347) at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.connectionClosed(TxConnectionListener.java:371) at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:574) at org.jboss.jca.adapters.jdbc.WrappedConnection.close(WrappedConnection.java:265) at org.teiid.translator.jdbc.JDBCExecutionFactory.closeConnection(JDBCExecutionFactory.java:287) at org.teiid.translator.jdbc.JDBCExecutionFactory.closeConnection(JDBCExecutionFactory.java:51) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.close(ConnectorWorkItem.java:226) [teiid-engine-8.4.2-redhat-1.jar:8.4.2-redhat-1] {code} It looks like it's only happening for the XML subplans. But it seems odd as we explicitly prevent close from being called multiple times on connector work item. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3434) Ability to enable/disable caching by table and/or source

by Burak Serdar (JIRA)

[ https://issues.jboss.org/browse/TEIID-3434?page=com.atlassian.jira.plugin... ] Burak Serdar updated TEIID-3434: -------------------------------- > Ability to enable/disable caching by table and/or source > -------------------------------------------------------- > > Key: TEIID-3434 > URL: https://issues.jboss.org/browse/TEIID-3434 > Project: Teiid > Issue Type: Feature Request > Reporter: Burak Serdar > Assignee: Steven Hawkins > > We need to be able to enable/disable caching by table and/or source. Some of our tables have real-time data, and we do not want to cache those, and some other tables can use cached data. It is not sufficient to use SQL options to turn caching on or off, because we're using 3rd party tools, and we don't have control over the SQL they generate. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3434) Ability to enable/disable caching by table and/or source

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3434?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3434: ------------------------------------- Then what you need is use PreparedPlan caching with Materialization defined on certain tables. For prepared plans you need to just use the Prepared Statement execution. > Ability to enable/disable caching by table and/or source > -------------------------------------------------------- > > Key: TEIID-3434 > URL: https://issues.jboss.org/browse/TEIID-3434 > Project: Teiid > Issue Type: Feature Request > Reporter: Burak Serdar > Assignee: Steven Hawkins > > We need to be able to enable/disable caching by table and/or source. Some of our tables have real-time data, and we do not want to cache those, and some other tables can use cached data. It is not sufficient to use SQL options to turn caching on or off, because we're using 3rd party tools, and we don't have control over the SQL they generate. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3434) Ability to enable/disable caching by table and/or source

by Burak Serdar (JIRA)

[ https://issues.jboss.org/browse/TEIID-3434?page=com.atlassian.jira.plugin... ] Burak Serdar updated TEIID-3434: -------------------------------- That is our problem: we don't have control over the query generated by the reporting tool, so we can't pass cache hints, or sql options. We'd like to be able to enable/disable caching by table and/or source. ----- Original Message ----- > Ability to enable/disable caching by table and/or source > -------------------------------------------------------- > > Key: TEIID-3434 > URL: https://issues.jboss.org/browse/TEIID-3434 > Project: Teiid > Issue Type: Feature Request > Reporter: Burak Serdar > Assignee: Steven Hawkins > > We need to be able to enable/disable caching by table and/or source. Some of our tables have real-time data, and we do not want to cache those, and some other tables can use cached data. It is not sufficient to use SQL options to turn caching on or off, because we're using 3rd party tools, and we don't have control over the SQL they generate. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3434) Ability to enable/disable caching by table and/or source

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3434?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3434: ------------------------------------- Yes, but they are two different things. PreparedPlan caching will get you statement cached, but it will execute every time. For resultset caching, you need to specify the /*+ cache */ hint in your user query then results will cached for specified time and scope(user, session or VDB). > Ability to enable/disable caching by table and/or source > -------------------------------------------------------- > > Key: TEIID-3434 > URL: https://issues.jboss.org/browse/TEIID-3434 > Project: Teiid > Issue Type: Feature Request > Reporter: Burak Serdar > Assignee: Steven Hawkins > > We need to be able to enable/disable caching by table and/or source. Some of our tables have real-time data, and we do not want to cache those, and some other tables can use cached data. It is not sufficient to use SQL options to turn caching on or off, because we're using 3rd party tools, and we don't have control over the SQL they generate. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2015