May 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Resolved: (TEIID-969) Time, date, and timestamp literals are being sent to Oracle as to_timestamp() regardless of their data type

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-969?page=com.atlassian.jira.plug... ] Steve Hawkins resolved TEIID-969. --------------------------------- Resolution: Out of Date Teiid no longer has a specific method for determining this conversion. The rewriter will push down a literal in the form of a timestamp for anything modeled as a timestamp (even if it's a source time). We rely on the driver, such as datadirect, to handle the conversion. > Time, date, and timestamp literals are being sent to Oracle as to_timestamp() regardless of their data type > ----------------------------------------------------------------------------------------------------------- > > Key: TEIID-969 > URL: https://jira.jboss.org/jira/browse/TEIID-969 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 6.0.0 > Environment: MMServer 5.5.3 > Oracle 10i > Oracle ANSI Connector > Reporter: Larry O'Leary > Assignee: Larry O'Leary > Fix For: 7.0 > > Attachments: mylyn-context.zip > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Source model uses a MetaMatrix type of timestamp and a native type of DATE. In prior releases this seems to have resulted in literal values that are being compared to the modeled column to be sent to Oracle as to_date(). Now, they are being sent as to_timestamp() which results in indexes being ignoreed for columns that are of DATE type. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-969) Time, date, and timestamp literals are being sent to Oracle as to_timestamp() regardless of their data type

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-969?page=com.atlassian.jira.plug... ] Steve Hawkins updated TEIID-969: -------------------------------- Fix Version/s: 7.0 Affects Version/s: 6.0.0 (was: 7.1) > Time, date, and timestamp literals are being sent to Oracle as to_timestamp() regardless of their data type > ----------------------------------------------------------------------------------------------------------- > > Key: TEIID-969 > URL: https://jira.jboss.org/jira/browse/TEIID-969 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 6.0.0 > Environment: MMServer 5.5.3 > Oracle 10i > Oracle ANSI Connector > Reporter: Larry O'Leary > Assignee: Larry O'Leary > Fix For: 7.0 > > Attachments: mylyn-context.zip > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Source model uses a MetaMatrix type of timestamp and a native type of DATE. In prior releases this seems to have resulted in literal values that are being compared to the modeled column to be sent to Oracle as to_date(). Now, they are being sent as to_timestamp() which results in indexes being ignoreed for columns that are of DATE type. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-171) Add SQL/XML support

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-171?page=com.atlassian.jira.plug... ] Steve Hawkins updated TEIID-171: -------------------------------- Fix Version/s: 7.0 (was: 7.1) Introducing initial support in 7.0 > Add SQL/XML support > ------------------- > > Key: TEIID-171 > URL: https://jira.jboss.org/jira/browse/TEIID-171 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.0 > > > We should add basic SQL./XML support to both create documents and extract rows from documents -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-972) Update sessionservice properties

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-972?page=com.atlassian.jira.plug... ] Steve Hawkins resolved TEIID-972. --------------------------------- Resolution: Out of Date The config.xml based session service no longer exists. > Update sessionservice properties > -------------------------------- > > Key: TEIID-972 > URL: https://jira.jboss.org/jira/browse/TEIID-972 > Project: Teiid > Issue Type: Task > Components: Documentation, Server > Affects Versions: 7.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The session service was simplified, we need to remove properties that are no longer in use. Only the following are still in use: > security.session.terminationHandlers > metamatrix.session.max.connections > metamatrix.session.time.limit > metamatrix.session.sessionMonitor.ActivityInterval -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-979) Add pushdown support for sql/xml functions

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-979?page=com.atlassian.jira.plug... ] Steve Hawkins updated TEIID-979: -------------------------------- Summary: Add pushdown support for sql/xml functions (was: Add support for Oracle XML queries in our Oracle connector) Fix Version/s: 7.1 Affects Version/s: 7.1 Description: We should have pushdown support for SQL/XML functionality. In particular Oracle and DB2 have support. see also case 5715 was: Oracle 9i and 10g have added special functionality for storing XML data, and for querying it. It would be good to use these special SQL statements to extract XML data from Oracle via our Oracle connector. case 5715 > Add pushdown support for sql/xml functions > ------------------------------------------ > > Key: TEIID-979 > URL: https://jira.jboss.org/jira/browse/TEIID-979 > Project: Teiid > Issue Type: Sub-task > Components: JDBC Connector > Affects Versions: 7.1 > Reporter: Marc Shirley > Assignee: Steve Hawkins > Fix For: 7.1 > > > We should have pushdown support for SQL/XML functionality. In particular Oracle and DB2 have support. > see also case 5715 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-979) Add support for Oracle XML queries in our Oracle connector

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-979?page=com.atlassian.jira.plug... ] Steve Hawkins updated TEIID-979: -------------------------------- Parent: TEIID-171 Issue Type: Sub-task (was: Feature Request) > Add support for Oracle XML queries in our Oracle connector > ---------------------------------------------------------- > > Key: TEIID-979 > URL: https://jira.jboss.org/jira/browse/TEIID-979 > Project: Teiid > Issue Type: Sub-task > Components: JDBC Connector > Reporter: Marc Shirley > > Oracle 9i and 10g have added special functionality for storing XML data, and for querying it. It would be good to use these special SQL statements to extract XML data from Oracle via our Oracle connector. > case 5715 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-979) Add support for Oracle XML queries in our Oracle connector

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-979?page=com.atlassian.jira.plug... ] Steve Hawkins reassigned TEIID-979: ----------------------------------- Assignee: Steve Hawkins > Add support for Oracle XML queries in our Oracle connector > ---------------------------------------------------------- > > Key: TEIID-979 > URL: https://jira.jboss.org/jira/browse/TEIID-979 > Project: Teiid > Issue Type: Sub-task > Components: JDBC Connector > Reporter: Marc Shirley > Assignee: Steve Hawkins > > Oracle 9i and 10g have added special functionality for storing XML data, and for querying it. It would be good to use these special SQL statements to extract XML data from Oracle via our Oracle connector. > case 5715 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-171) Add SQL/XML support

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-171?page=com.atlassian.jira.plug... ] Steve Hawkins updated TEIID-171: -------------------------------- Summary: Add SQL/XML support (was: Add SQLXML Function for Extract()) Description: We should add basic SQL./XML support to both create documents and extract rows from documents (was: We had a posting on the dev site (http://devcentral.metamatrix.com/node/2089809383) asking how they can retrieve an entire xml node from an input doc in a web service transformation instead of just the node text. Our current xPath function xPathValue() always return the text. We need something more like SQLXML extract()/extractvalue() so we can return the xml OR the text.) Complexity: High (was: Medium) > Add SQL/XML support > ------------------- > > Key: TEIID-171 > URL: https://jira.jboss.org/jira/browse/TEIID-171 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.1 > > > We should add basic SQL./XML support to both create documents and extract rows from documents -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-953) document the use of cluster.key

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-953?page=com.atlassian.jira.plug... ] Steve Hawkins resolved TEIID-953. --------------------------------- Resolution: Out of Date We no long rely on teiid using a shared key. > document the use of cluster.key > ------------------------------- > > Key: TEIID-953 > URL: https://jira.jboss.org/jira/browse/TEIID-953 > Project: Teiid > Issue Type: Task > Components: Documentation > Affects Versions: 7.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Original Estimate: 1 day > Remaining Estimate: 1 day > > Update the docs to remove usage of metamatrixpki.keystore in favor of the cluster.key -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-954) Need method to controll max amount of bufer disk space

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-954?page=com.atlassian.jira.plug... ] Steve Hawkins updated TEIID-954: -------------------------------- Issue Type: Quality Risk (was: Bug) Fix Version/s: 7.1 Affects Version/s: 6.0.0 > Need method to controll max amount of bufer disk space > ------------------------------------------------------ > > Key: TEIID-954 > URL: https://jira.jboss.org/jira/browse/TEIID-954 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 7.1 > > > There needs to be a configurable limit to how much disk space buffer manager is able to use. > Currently, you can specify the limit per file and the limit of how many files buffer manager can have open at one time, but there is no means of keeping buffer manager for eating up all the available disk space and then resulting in unpredictable behavior and stability. > It's fine if queries that need the file buffer manager but find it is full fail outright when it is full. -- 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, 11 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 2010