February 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Assigned: (TEIID-959) Database bundle and schemas should be an optional component of Getting Started kit

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-959?page=com.atlassian.jira.plug... ] Van Halbert reassigned TEIID-959: --------------------------------- Assignee: Van Halbert > Database bundle and schemas should be an optional component of Getting Started kit > ---------------------------------------------------------------------------------- > > Key: TEIID-959 > URL: https://jira.jboss.org/jira/browse/TEIID-959 > Project: Teiid > Issue Type: Task > Components: Documentation > Affects Versions: 7.1 > Reporter: Larry O'Leary > Assignee: Van Halbert > > We need to bundle a database along with the schemas that are to be used with the Getting Started kit. The bundle should be a self-contained database installation along with the MMFinancials schema pre-loaded into it. > The idea is that a user can simply run a script or installer that will place all the necessary database components along with a predetermined configuration on the user's target machine so that they can be up and running with the tutorials much faster without the need to involve a DBA. -- 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

14 years, 10 months

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-972?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-996 to TEIID-972: ------------------------------------------ Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-972 (was: JBEDSP-996) Component/s: Documentation Server (was: Documentation) (was: Server) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: 5.5.3) > 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

14 years, 10 months

1
0
0 / 0

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

by Van Halbert (JIRA)

Time, date, and timestamp literals are being sent to Oracle as to_timestamp() regardless of their data type ----------------------------------------------------------------------------------------------------------- Key: TEIID-971 URL: https://jira.jboss.org/jira/browse/TEIID-971 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 7.1 Environment: MMServer 5.5.3 Oracle 10i Oracle ANSI Connector Reporter: Larry O'Leary Assignee: Larry O'Leary 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-970) XML Connector doc still describes using the cache to cache exact query matches and eliminate trips to source.

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-970?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1148 to TEIID-970: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-970 (was: JBEDSP-1148) Component/s: Documentation (was: Documentation) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: 5.5.4) (was: 5.5.3) > XML Connector doc still describes using the cache to cache exact query matches and eliminate trips to source. > ------------------------------------------------------------------------------------------------------------- > > Key: TEIID-970 > URL: https://jira.jboss.org/jira/browse/TEIID-970 > Project: Teiid > Issue Type: Bug > Components: Documentation > Affects Versions: 7.1 > Reporter: John Doyle > Assignee: John Doyle > > The cache was change in 5.5.3 so that cached documents are not shared across top level queries. The cache is only there to support joins now. -- 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

14 years, 10 months

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-969?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1142 to TEIID-969: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-969 (was: JBEDSP-1142) Component/s: JDBC Connector (was: Connectors) Fix Version/s: (was: Westport) (was: 5.5.3) (was: 5.5.4) Affects Version/s: 7.1 (was: 5.5.3) (was: 5.5.4) > 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: 7.1 > Environment: MMServer 5.5.3 > Oracle 10i > Oracle ANSI Connector > Reporter: Larry O'Leary > Assignee: Larry O'Leary > 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

14 years, 10 months

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-968?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1143 to TEIID-968: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-968 (was: JBEDSP-1143) Component/s: (was: Connectors) (was: Query) Fix Version/s: (was: Westport) (was: 5.5.3) (was: 5.5.4) Affects Version/s: 7.1 (was: 5.5.3) (was: 5.5.4) > 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/jira/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: Larry O'Leary > 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-967) Asynchronous messaging API

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-967?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-173 to TEIID-967: ------------------------------------------ Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-967 (was: JBEDSP-173) Component/s: Documentation (was: Documentation) Fix Version/s: (was: Westport) > Asynchronous messaging API > -------------------------- > > Key: TEIID-967 > URL: https://jira.jboss.org/jira/browse/TEIID-967 > Project: Teiid > Issue Type: Feature Request > Components: Documentation > Reporter: Marc Shirley > Assignee: Jerry Helbling > Priority: Minor > -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-966) User (principal) name in MetaMatrix should be consistently the same string

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-966?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1097 to TEIID-966: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-966 (was: JBEDSP-1097) Component/s: Query Engine (was: Server) Fix Version/s: (was: Westport) Affects Version/s: (was: 5.5.2) (was: 5.5.3) (was: 5.5.1) (was: 5.5) > User (principal) name in MetaMatrix should be consistently the same string > -------------------------------------------------------------------------- > > Key: TEIID-966 > URL: https://jira.jboss.org/jira/browse/TEIID-966 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > The issue has to do with the way we represent a user's name. Customer uses LDAP for a membership domain. Sometimes, the user's name is their cn, followed by "@" plus the domain name, e.g.: > username@LDAP > Sometimes, it's simply the user name. e.g.: > username > This name is recorded in the audit logs, used throughout Console, and perhaps most importantly, is the name returned by the USER() system function. > The problem is that we use the return value of USER() to record information about who is doing things. Later, we make comparisons against this info to control access, etc. This comparison often fails, even though we may be comparing the same identity, due to this inconsistency. > Workaround for the USER() function: build in special logic within each procedure to strip out the @LDAP if it is present. -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-965) Need Excel file importer / connector

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-965?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-922 to TEIID-965: ------------------------------------------ Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-965 (was: JBEDSP-922) Component/s: (was: Connectors) Fix Version/s: (was: PostWestport) Affects Version/s: (was: 5.5) > Need Excel file importer / connector > ------------------------------------ > > Key: TEIID-965 > URL: https://jira.jboss.org/jira/browse/TEIID-965 > Project: Teiid > Issue Type: Feature Request > Reporter: Steven Hawkins > > Really need to add an Excel connector in SP1. The easiest way to do this is probably with one of the open source JDBC drivers that work over Excel files. > Something like: > https://xlsql.dev.java.net/ - Excel JDBC driver (GPL unfortunately, so we probably can't distribute the driver) > http://www.andykhan.com/jexcelapi/ - Java Excel API (GPL too) > http://xlsjdbc.sourceforge.net/ - LGPL (uses Apache POI), really cheesy and maybe not being updated > http://jakarta.apache.org/poi/ - Excel API, event-based and not particularly friendly > http://www.vistaportal.com/products/vistajdbc-QA.htm - commercial -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-964) Must pushdown functions in select clause

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-964?page=com.atlassian.jira.plug... ] Van Halbert moved JBEDSP-1159 to TEIID-964: ------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-964 (was: JBEDSP-1159) Component/s: Query Engine (was: Query) Fix Version/s: (was: Westport) Affects Version/s: (was: 5.5) > Must pushdown functions in select clause > ---------------------------------------- > > Key: TEIID-964 > URL: https://jira.jboss.org/jira/browse/TEIID-964 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > > (F_ATM_REPORT_TYPE is a DB function) > SELECT F_ATM_REPORT_TYPE (BUS_LINE_CODE) FROM ... > Will not have the function pushed down if it only appears in the select clause. The planner must check if a function is pushdown only when it appears in the select clause and determine a source to push it to. -- 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

14 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2010