February 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1850) Add support for GreenPlum Database as a source

by Ken Johnson (Created) (JIRA)

Add support for GreenPlum Database as a source ---------------------------------------------- Key: TEIID-1850 URL: https://issues.jboss.org/browse/TEIID-1850 Project: Teiid Issue Type: Feature Request Affects Versions: 7.5 Reporter: Ken Johnson Assignee: Steven Hawkins Consider adding (or perhaps just validating) support for Greenplum. It's based on Postgres and uses the PG jdbc driver. Community version available for download. -- 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

11 years, 8 months

3
4
0 / 0

[JBoss JIRA] (TEIID-1871) Teiid is handling MySQL5.0 returning DAYNAME as a blob

by Paul Nittel (Created) (JIRA)

Teiid is handling MySQL5.0 returning DAYNAME as a blob ------------------------------------------------------ Key: TEIID-1871 URL: https://issues.jboss.org/browse/TEIID-1871 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Reporter: Paul Nittel Assignee: Steven Hawkins Attachments: mysql-connector-java-5.0.8-bin.jar, QT_MySql50_Push-ds.xml, QT_MySql50_Push.vdb SELECT IntKey, DAYNAME(datevalue) FROM BQT1.SmallA ORDER BY IntKey LIMIT 10 Fails with: Caught SQLException: Invalid conversion from type class org.teiid.core.types.BlobType with value 'javax.sql.rowset.serial.SerialBlob@6482112e' to type class java.lang.String Dev indicaters, "The driver returns the bytes, which we treat as a blob. We have an explicit workaround in the translator for the char function, but I've never seen this outside of the char function. There may be an issue with the http://dev.mysql.com/doc/refman/5.5/en/server-system-variables.html#sysva... setting also that could influence how the value is returned." The server setting is en_US. -- 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

11 years, 8 months

6
12
0 / 0

[JBoss JIRA] (TEIID-1840) The Jdbc Socket Host Name Propertie cannot be changed in admin console

by Nagai Eiichi (Created) (JIRA)

The Jdbc Socket Host Name Propertie cannot be changed in admin console ---------------------------------------------------------------------- Key: TEIID-1840 URL: https://issues.jboss.org/browse/TEIID-1840 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 7.4 Reporter: Nagai Eiichi Assignee: Steven Hawkins The Jdbc Socket Host Name property cannot be changed in admin console. -- 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

11 years, 8 months

6
6
0 / 0

[JBoss JIRA] (TEIID-1951) CommandLogging is refers to the old MMx connectorBindingName, when it should refer to it a translator

by Van Halbert (JIRA)

Van Halbert created TEIID-1951: ---------------------------------- Summary: CommandLogging is refers to the old MMx connectorBindingName, when it should refer to it a translator Key: TEIID-1951 URL: https://issues.jboss.org/browse/TEIID-1951 Project: Teiid Issue Type: Bug Components: Documentation, Server Affects Versions: 7.4.1 Reporter: Van Halbert Assignee: Van Halbert Priority: Minor In the command logging, the translator is still be referred to as the connectorBindingName: 2012-02-22 16:01:53,712 DEBUG [org.teiid.COMMAND_LOG] (Worker1_QueryProcessorQueue11 START DATA SRC COMMAND: startTime=2012-02-22 16:01:53.712 requestID=Ku4/dgtZPYk0.5 sourceCommandID=4 txID=null modelName=DTHCP connectorBindingName=jdbc-simple sessionID=Ku4/dgtZPYk0 principal=user@teiid-security sql=HCP_ADDR_XREF.HUB_ADDR_ID, CPN_PROMO_HIST.PROMO_STAT_DT FROM CPN_PROMO_HIST, HCP_ADDRESS, HCP_ADDR_XREF WHERE (HCP_ADDRESS.ADDR_ID = CPN_PROMO_HIST.SENT_ADDR_ID) AND (HCP_ADDRESS.ADDR_ID = HCP_ADDR_XREF.ADDR_ID) AND (CPN_PROMO_HIST.PROMO_STAT_CD NOT LIKE 'EMAIL%') AND (CPN_PROMO_HIST.PROMO_STAT_CD <> 'SENT_EM') AND (CPN_PROMO_HIST.PROMO_STAT_DT > {ts'2010-02-22 16:01:52.928'}) Also, it would be good to include an example of this output in the documentation of what will be seen. -- 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

11 years, 8 months

2
6
0 / 0

[JBoss JIRA] (TEIID-1911) Deploy time cached VDB metadata is being deleted during shutdown.

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-1911: ----------------------------------- Summary: Deploy time cached VDB metadata is being deleted during shutdown. Key: TEIID-1911 URL: https://issues.jboss.org/browse/TEIID-1911 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Critical Fix For: 8.0 Due to https://issues.jboss.org/browse/AS7-3431 the metadata is always being deleted during the shutdown. This will be bigger issue with dynamic VDBs. -- 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

11 years, 8 months

2
6
0 / 0

[JBoss JIRA] (TEIID-1935) TransformationMetadata.getXMLSchemas relative paths fail on windows

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-1935: ------------------------------------- Summary: TransformationMetadata.getXMLSchemas relative paths fail on windows Key: TEIID-1935 URL: https://issues.jboss.org/browse/TEIID-1935 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.7 The use of File logic makes getting the parent path dependent on the platform. The logic is only currently correct for filesystems that use the / separator. -- 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

11 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1751) Scalar function reference issues

by Steven Hawkins (JIRA)

Scalar function reference issues -------------------------------- Key: TEIID-1751 URL: https://issues.jboss.org/browse/TEIID-1751 Project: Teiid Issue Type: Bug Components: Documentation Affects Versions: 7.4.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4.1, 7.6 Generic issue for on-going corrections/improvements to scalar function docs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
3
0 / 0

[JBoss JIRA] (TEIID-1944) After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist

by Van Halbert (JIRA)

Van Halbert created TEIID-1944: ---------------------------------- Summary: After changing model to replace primary key with a unique key, the deployment of the vdb errors saying PrimaryKey does not exist Key: TEIID-1944 URL: https://issues.jboss.org/browse/TEIID-1944 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.4.1 Reporter: Van Halbert Assignee: Steven Hawkins Attachments: dummy-ds.xml, server.log, Trade.vdb In designer, I removed a primary key and replaced it with a unique key, and changed the foreign key to now reference the unique key, and all built with no errors. When deploying vdb to server, you see this exception (partial, see attachment for full log): Caused by: mmuuid:15f67b60-e387-4092-bbc5-0b7726585f52 PrimaryKey does not exist. at org.teiid.metadata.index.IndexMetadataFactory.getPrimaryKey(IndexMetadataFactory.java:353) at org.teiid.metadata.index.IndexMetadataFactory.getTables(IndexMetadataFactory.java:295) -- 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

11 years, 8 months

2
6
0 / 0

[JBoss JIRA] (TEIID-1893) TeiidException when executing SELECT subquery with more than 2 UNIONs

by Andriy Rokhmanov (Created) (JIRA)

TeiidException when executing SELECT subquery with more than 2 UNIONs --------------------------------------------------------------------- Key: TEIID-1893 URL: https://issues.jboss.org/browse/TEIID-1893 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Environment: Windows 7, JBoss 5.1.0.GA, java version "1.6.0_22" 64 bit Reporter: Andriy Rokhmanov Assignee: Steven Hawkins Exception: org.teiid.core.TeiidException happens after executing select statement #1, but works fine on #2 and #3. The execution plan for problematic statement attached. 1. Problematic SQL Statement: SELECT T.ROLE_NAME as ROLE_NAME, T.SCHEMA_NAME as SCHEMA_NAME, T.INSTALL_STATUS as INSTALL_STATUS FROM ( SELECT ROLE_NAME, 'demodata_chorus_metadata' as SCHEMA_NAME, INSTALL_STATUS from demodata_chorus_metadata.chorus_role UNION SELECT ROLE_NAME, 'security_cia_chorus_metadata' as SCHEMA_NAME, INSTALL_STATUS from security_cia_chorus_metadata.chorus_role UNION SELECT ROLE_NAME, 'vantage_chorus_metadata' as SCHEMA_NAME, INSTALL_STATUS from vantage_chorus_metadata.chorus_role ) AS T, chorus_license.RL_LICENSE as L WHERE T.ROLE_NAME = L.ROLE_NAME AND T.install_status = true; 2. This SQL statement works fine (the difference between #1 and #2 is in final 'AND...' clause): SELECT T.ROLE_NAME as ROLE_NAME, T.SCHEMA_NAME as SCHEMA_NAME, T.INSTALL_STATUS as INSTALL_STATUS FROM ( SELECT ROLE_NAME, 'demodata_chorus_metadata' as SCHEMA_NAME, INSTALL_STATUS from demodata_chorus_metadata.chorus_role UNION SELECT ROLE_NAME, 'security_cia_chorus_metadata' as SCHEMA_NAME, INSTALL_STATUS from security_cia_chorus_metadata.chorus_role UNION SELECT ROLE_NAME, 'vantage_chorus_metadata' as SCHEMA_NAME, INSTALL_STATUS from vantage_chorus_metadata.chorus_role ) AS T, chorus_license.RL_LICENSE as L WHERE T.ROLE_NAME = L.ROLE_NAME; 3. This SQL statement also works fine (the difference between #1 and #3 is only two UNIONs included out of three, does not matter which ones) SELECT T.ROLE_NAME as ROLE_NAME, T.SCHEMA_NAME as SCHEMA_NAME, T.INSTALL_STATUS as INSTALL_STATUS FROM ( SELECT ROLE_NAME, 'security_cia_chorus_metadata' as SCHEMA_NAME, INSTALL_STATUS from security_cia_chorus_metadata.chorus_role UNION SELECT ROLE_NAME, 'vantage_chorus_metadata' as SCHEMA_NAME, INSTALL_STATUS from vantage_chorus_metadata.chorus_role ) AS T, chorus_license.RL_LICENSE as L WHERE T.ROLE_NAME = L.ROLE_NAME AND T.install_status = true; -- 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

11 years, 8 months

5
4
0 / 0

[JBoss JIRA] (TEIID-1865) Thread-safe JDBC connection

by Mark Addleman (Created) (JIRA)

Thread-safe JDBC connection --------------------------- Key: TEIID-1865 URL: https://issues.jboss.org/browse/TEIID-1865 Project: Teiid Issue Type: Feature Request Reporter: Mark Addleman Assignee: Steven Hawkins I would like to share an embedded Teiid JDBC connection across multiple threads without the JDBC client worrying about synchronization. For more detail, see forum discussion http://community.jboss.org/message/641133#641133 -- 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

11 years, 8 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2012