August 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1117) When VDBis deleted the cached medata files are not cleaned up

by Ramesh Reddy (JIRA)

When VDBis deleted the cached medata files are not cleaned up ------------------------------------------------------------- Key: TEIID-1117 URL: https://jira.jboss.org/browse/TEIID-1117 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 When the VDB deployed the metadata files are cached inside the "data/teiid/<vdb-name>" directory. However, when the VDB is deleted these files are not cleaned up automatically. If user deletes the VDB and re-deploys a new VDB, the server will still look at the old metadata files. -- 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

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1041) Create a CTC kit to be used to deploy Teiid/EDS query testing across all supported platforms in the Hudson QA Lab

by Warren Gibson (JIRA)

Create a CTC kit to be used to deploy Teiid/EDS query testing across all supported platforms in the Hudson QA Lab ----------------------------------------------------------------------------------------------------------------- Key: TEIID-1041 URL: https://jira.jboss.org/jira/browse/TEIID-1041 Project: Teiid Issue Type: Task Components: Integration Tests Affects Versions: 7.0 Reporter: Warren Gibson Assignee: Van Halbert A CTC kit is needed to deploy Teiid/EDS query testing across all supported platforms in the Hudson QA Lab -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (TEIID-1107) Fix RulePlanJoins to do better push down when Teiid functions are in criteria

by Jerry Helbling (JIRA)

Fix RulePlanJoins to do better push down when Teiid functions are in criteria ----------------------------------------------------------------------------- Key: TEIID-1107 URL: https://jira.jboss.org/browse/TEIID-1107 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Jerry Helbling Assignee: Steven Hawkins Priority: Minor Since a SELECT with criteria that includes a call to a Teiid function (for example formatDate) cannot be pushed down to a source, the aim of this modification is to move the SELECT so that it will not prevent other parts of the query from being pushed down. -- 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

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Closed: (TEIID-108) xsd type conversion should be consistent

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-108?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-108. ------------------------------- > xsd type conversion should be consistent > ---------------------------------------- > > Key: TEIID-108 > URL: https://jira.jboss.org/browse/TEIID-108 > Project: Teiid > Issue Type: Bug > Components: SOAP Services, XML Connector > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 7.1 > > > Defect Tracker #23654: [This came from our consultant Jimmy Fernandez' Case 4795, for customer MITRE]. > Jimmy wrote: "When modeling Web Services with our Web Service to relational importer and the column type on the request table out are dateTime objects; the SOAP/XML connectors should be converting the specific column to the xsd:dateTime object specifications. It would not hurt to ensure that we are following the correct specification for other xsd objects as well." -- 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

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-874) Wiki documentation on SSL Encryption is misleading

by Nestor D. Rodriguez (JIRA)

Wiki documentation on SSL Encryption is misleading -------------------------------------------------- Key: TEIID-874 URL: https://jira.jboss.org/jira/browse/TEIID-874 Project: Teiid Issue Type: Quality Risk Components: Server Affects Versions: 6.2.0 Environment: N/A Reporter: Nestor D. Rodriguez Assignee: Steven Hawkins Priority: Minor The wiki page describing how to implement SSL in Teiid (https://www.jboss.org/community/wiki/secureclientconnectionsusingsslinteiid) implies that the keystore and trustore password properties (ssl.keystore.Password and ssl.truststore.Password) can be entered in cleartext. The code, on the other hand, requires them to be encrypted, using the strategy described in http://www.jboss.org/community/wiki/EncryptingpasswordsinTeiid The documentation needs to be modified to reflect that. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

4
3
0 / 0

[JBoss JIRA] Closed: (TEIID-886) Request for more statistical functions in Teiid

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-886?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-886. ------------------------------- > Request for more statistical functions in Teiid > ----------------------------------------------- > > Key: TEIID-886 > URL: https://jira.jboss.org/browse/TEIID-886 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.2.0 > Reporter: Debbie Steigner > Fix For: 7.1 > > > Please provide a richer set of aggregate functions, specifically statistical functions like population standard deviation, sample standard deviation, population standard variance, etc. -- 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

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-914) OnWrapTransactionTests.testMultipleSourceTimeout test fails due to due to execpted error message is different

by Van Halbert (JIRA)

OnWrapTransactionTests.testMultipleSourceTimeout test fails due to due to execpted error message is different ------------------------------------------------------------------------------------------------------------- Key: TEIID-914 URL: https://jira.jboss.org/jira/browse/TEIID-914 Project: Teiid Issue Type: Bug Components: Integration Tests Affects Versions: 7.0 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Minor The OnWrapTransactionTests.testMultipleSourceTimeout test fails due to expected message is different. It appears the upstream error being thrown by sendRequestMessageAndWait(..) in MMStatement.executeSql(String[] commands, boolean isBatchedCommand, Boolean requiresResultSet) has changed. If I take the message from the caught exception and prepend to the created message and use that message in the MMSQLException throw, then the test passes. Also, another problem with the current error message is that it gives no indication as to the problem why the statement cannot run, it only provides a general message, ilke the following: "Error trying to execute a statement [insert into pm1.g1 (e1, e2) values(600,'600'), insert into pm1.g2 (e1, e2) values (600,'600') .........." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Closed: (TEIID-968) Timestamp literals with fractional seconds result in source query execution performance when being compared to less percise time types

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-968?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-968. ------------------------------- > Timestamp literals with fractional seconds result in source query execution performance when being compared to less percise time types > -------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-968 > URL: https://jira.jboss.org/browse/TEIID-968 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 7.1 > Environment: MM 5.5.3 > Oracle 10i > Oracle ANSI Connector > Reporter: Larry O'Leary > Assignee: Steve Hawkins > Fix For: 7.1 > > Attachments: mylyn-context.zip > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Seeing that the only "time" type for MetaMatrix is timestamp and Oracle uses DATE to store time and TIMESTAMP to store time with fractional seconds we need a method of sending a timestamp as a literal that Oracle can use as a DATE instead of requiring the comparison to be normalized to TIMESTAMP as this results in a huge performance hit within Oracle. > It is possible to change this behaviour by actually setting a date only column to MetaMatrix date in the model but this does not account for situations where a DATE column in Oracle holds date and time information. In those cases, I would still need to use timestamp for MetaMatrix and this would result in a huge performance impact. > Oracle will automatically use the widest type possible when doing comparisons so if I store date only data in a DATE column and then attempt to query using criteria on that column such ad {d'2000-01-01'} the date literal gets converted to {ts'2000-01-01 00:00:00.0'} prior to it being sent to Oracle. This will result in Oracle converting my DATE column into a TIMESTAMP column to handle the comparison. > The current DataDirect driver we are using actually accounts for this issue when dealing with timestamp literals. Basically, if the timestamp literal does not include fractional seconds, the driver will pass it to Oracle as a date instead of a timestamp. This greatly improves performance in these situations. > So, if the current logic is kept, but we simply truncate the timestamp literal to remove the fractional seconds, we get the advantage of the driver performing better type mapping in this situation. -- 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

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-831) Stored procedure execution fails with with out parameters after in

by Steven Hawkins (JIRA)

Stored procedure execution fails with with out parameters after in ------------------------------------------------------------------ Key: TEIID-831 URL: https://jira.jboss.org/jira/browse/TEIID-831 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 Stored procedure execution, such as the fakemetadata pm2.sptest8 fail with with out parameters after in. This is due to skipping the index increment for in parameters. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-715) Allow the user to set null ordering behavior

by Steven Hawkins (JIRA)

Allow the user to set null ordering behavior -------------------------------------------- Key: TEIID-715 URL: https://jira.jboss.org/jira/browse/TEIID-715 Project: Teiid Issue Type: Feature Request Components: Connector API, Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3.0 Sources that support order by may have different null ordering behavior than Teiid (which currently treats null as low). We should support the option for the server to be configured as nulls high, low, always high, or always low. Connectors will need to indicate the sort mode they support so the appropriate push-down and compensating actions can be taken. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2010