[JBoss JIRA] Created: (TEIID-1750) Memory handling improvements
by Steven Hawkins (JIRA)
Memory handling improvements
----------------------------
Key: TEIID-1750
URL: https://issues.jboss.org/browse/TEIID-1750
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.6
The buffermanager will create softreferences for batches that prefer memory, but does not track the memory as held once the value has been passivated.
Also small lobs, such as xml values created via sqlxml, should be inlined into results for greater performance - and so that they can be paged out by the buffermanager rather than being held by a lobmanager.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIID-1928) PSQL emulation layer has problems converting timestamp '0000
by Graeme Gillies (JIRA)
Graeme Gillies created TEIID-1928:
-------------------------------------
Summary: PSQL emulation layer has problems converting timestamp '0000
Key: TEIID-1928
URL: https://issues.jboss.org/browse/TEIID-1928
Project: Teiid
Issue Type: Bug
Affects Versions: 7.6
Environment: java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.10) (rhel-1.23.1.9.10.el5_7-x86_64)
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
on
Red Hat Enterprise Linux Server
Teiid 7.6
Perl client running on either Fedora 16 or RHEL 5.7
Using perl-DBD-Pg-2.18.0-3.fc16.x86_64
Reporter: Graeme Gillies
Assignee: Steven Hawkins
When we attempt to run the following query against our teiid 7.6 install we get an error about converting timestamps. Note this only seems to affect the PSQL emulation layer, jdbc layer is fine
{noformat}
EngVDBF=> select * from orgchart2s.history;
ERROR: Error Code:S1009 Message:OrgChart2DS: Error Code:S1009 Message:Unexpected exception while translating results: Cannot convert value '0000-00-00 00:00:00' from column 6 to TIMESTAMP.
DETAIL: org.teiid.jdbc.TeiidSQLException: Error Code:S1009 Message:OrgChart2DS: Error Code:S1009 Message:Unexpected exception while translating results: Cannot convert value '0000-00-00 00:00:00' from column 6 to TIMESTAMP.
EngVDBF=>
{noformat}
It looks like there is a problem converting a timestamp of '0000-00-00 00:00:00'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIID-1828) Dependent critiera in query plan but missing in actual query and additional information is provided
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1828?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-1828.
---------------------------------
> Dependent critiera in query plan but missing in actual query and additional information is provided
> ---------------------------------------------------------------------------------------------------
>
> Key: TEIID-1828
> URL: https://issues.jboss.org/browse/TEIID-1828
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Affects Versions: 7.4.1
> Environment: Oracle datasource, but likely all
> Reporter: Tom Fonteyne
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 7.6
>
>
> tested on EDS 5.2 ER3 and ER6, same results:
> We're running a query which has two sets of dependent criteria in one of the queries. The plan looks ok, and in the command log we see that EDS is getting both sets of dependent criteria and bringing back rows which we would expect to be passed into the final query.
> The problem is that the final query has 1=1 in the place of where the dependent criteria should be.
> In the plan:
> + Query:SELECT g_0.account_code AS c_0, g_0.book_code AS c_1, SUM(g_0.func_amount) AS c_2 FROM TSL_SQL_Source.TSL.TSL_FINANCIAL_ACCOUNT_ITEMS_T2 AS g_0 WHERE (g_0.business_date = {d'2011-06-29'}) AND (g_0.account_code IN (<dependent values>)) AND (g_0.book_code IN (<dependent values>)) GROUP BY g_0.account_code, g_0.book_code ORDER BY c_0 NULLS FIRST
> The source specific query from the command log:
> 2011-11-14 11:35:35,313 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue60) Source-specific command: SELECT g_0.ACCOUNT_CODE AS c_0, g_0.BOOK_CODE AS c_1, SUM(g_0.FUNC_AMOUNT) AS c_2 FROM TSL_FINANCIAL_ACCOUNT_ITEMS_T2 g_0 WHERE g_0.BUSINESS_DATE = {d '2011-06-29'} AND 1 = 1 AND 1 = 1 GROUP BY g_0.ACCOUNT_CODE, g_0.BOOK_CODE ORDER BY c_0 NULLS FIRST
> Stats should be correct in the VDB. We also updated the stats using the system procedures just before executing the query.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months