March 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-392) Salesforce connector should be able to call QueryAll

by John Doyle (JIRA)

Salesforce connector should be able to call QueryAll ---------------------------------------------------- Key: TEIID-392 URL: https://jira.jboss.org/jira/browse/TEIID-392 Project: Teiid Issue Type: Feature Request Components: Salesforce Connector Reporter: John Doyle Assignee: John Doyle A customer has a requirement to be able to see all SF objects of a type, even if they have been deleted. The queryall method in the SF API exists for this purpose and the connector needs to expose this call in some manner. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-416) Create Hibernate Dialect for Teiid

by Ramesh Reddy (JIRA)

Create Hibernate Dialect for Teiid ---------------------------------- Key: TEIID-416 URL: https://jira.jboss.org/jira/browse/TEIID-416 Project: Teiid Issue Type: Feature Request Components: Build/Kits, JDBC Driver Affects Versions: 6.x Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.1.0 Create Hibernate dialect for Teiid. -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-440) Capture the vendor SQLSTATE code, if the connector connection fails

by Ramesh Reddy (JIRA)

Capture the vendor SQLSTATE code, if the connector connection fails ------------------------------------------------------------------- Key: TEIID-440 URL: https://jira.jboss.org/jira/browse/TEIID-440 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Trivial Fix For: 6.1.0 Currently when the JDBC connector fails to make the connection, we correctly unroll the SQLException, but do not provide the SQLSTATE code on to the wrapping exception's description, so that it is visible in the Teiid's logs. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-379) MySQL connector assumes that database is running in ANSI mode rather than the default mode

by Greg Haber (JIRA)

MySQL connector assumes that database is running in ANSI mode rather than the default mode ------------------------------------------------------------------------------------------ Key: TEIID-379 URL: https://jira.jboss.org/jira/browse/TEIID-379 Project: Teiid Issue Type: Bug Components: JDBC Connector Environment: Teiid trunk as of 2/23/09 at 3:22 PM eastern Reporter: Greg Haber Assignee: Steven Hawkins I noticed with the legacy MetaMatrix product that our MySQL connector seems to assume that it is connecting to a MySQL database running in "ANSI" SQL mode For instance, we list in the capabilities class that MySQL supports || as a string concatenation parameter, but it actually only supports it if the SQL mode "PIPES_AS_CONCAT" is set - and this is one of the individual modes that gets set when you set the "ANSI" meta-mode (see http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html#sqlmode_ansi for details). This is a bad assumption as it is not the default setting for MySQL (the default sql-mode setting is "", or no special modes). I took a look at some of the databases used at Red Hat for testing MetaMatrix for MySQL (specifically, slntds03) and noticed that they have sql-mode set to ANSI on the server side. I took a look at the current Teiid trunk code and it is the same as the legacy MetaMatrix code in this regard, so Teiid has the same issue. Two possible resolutions are: -Rework the connector to remove any assumptions that sql-mode=ANSI -set sql-mode to ANSI when establishing new connections to MySQL (this can be done by sending the SQL statement 'set SESSION sql-mode="ANSI" after establishing a connection). Unfortunately there does not appear to be a way to set this mode via a JDBC connection property - you need to send the "set" command after establishing the connection. -- 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, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIID-427) Access file error exception when RuntimeIndexSelector trying to load indexes from zip file

by Salvatore Incandela (JIRA)

Access file error exception when RuntimeIndexSelector trying to load indexes from zip file ------------------------------------------------------------------------------------------ Key: TEIID-427 URL: https://jira.jboss.org/jira/browse/TEIID-427 Project: Teiid Issue Type: Bug Affects Versions: 6.0.0 Environment: Ubuntu 8.10, Eclipse 3.4.2, Java 1.6.0.12 Reporter: Salvatore Incandela Assignee: Steven Hawkins loadIndexesFromZipFile() method extract folders as file, during the unzip process, this cause an access file error, because the directories will included into the array indexes. [code] File entryFile = new File(getIndexDirectoryPath(), entry.getName()); FileUtils.write(zipInputStream, entryFile, length); if (SimpleIndexUtil.indexFileExists(entryFile)) { tmp.add(new Index(entryFile.getAbsolutePath(), true)); } [/code] I tried a this solution, it seems to work: [code] File entryFile = new File(getIndexDirectoryPath(), entry.getName()); if (entry.isDirectory()) { entryFile.mkdir(); } else { FileUtils.write(zipInputStream, entryFile, length); } if (SimpleIndexUtil.indexFileExists(entryFile)) { tmp.add(new Index(entryFile.getAbsolutePath(), true)); } [/code] In this case the indexFileExist() excludes all the directories, form the array indexes. -- 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, 7 months

2
11
0 / 0

[JBoss JIRA] Created: (TEIID-436) Error Installing Teiid with a Postgres Repository

by Ted Jones (JIRA)

Error Installing Teiid with a Postgres Repository ------------------------------------------------- Key: TEIID-436 URL: https://jira.jboss.org/jira/browse/TEIID-436 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 6.0.0 Reporter: Ted Jones Assignee: Steven Hawkins While running setupmm with a local Postgres repository, I encountered the following fatal error: /home/tejones/apps/EnterpriseDataServicesPlatform/03202009/server-0.0.1-SNAPSHOT/config/install/setup_server.xml:453: [MetaMatrixComponentException] ERR.014.004.0054: Error inserting extension module Next Startup using SQL statement: INSERT INTO CS_EXT_FILES(FILE_UID,CHKSUM,FILE_NAME,SEARCH_POS,IS_ENABLED,FILE_DESC,CREATED_BY,CREATION_DATE,UPDATED_BY,UPDATE_DATE,FILE_TYPE) VALUES 1 [DBIDGeneratorException] ERR.003.013.0011: Error creating id for CS_EXT_FILES context. 2 [DBIDGeneratorException] ERR.003.013.0014: Could not obtain a unique ID blocksize of 100 for context CS_EXT_FILES. 3 [ManagedConnectionException] ERR.003.013.0016: Unable to obtain the managed connection for the DBID transaction 4 [MetaMatrixException] ERR.003.015.0003: JDBCPlatform Program Error, unable to create platform. 5 [MetaMatrixException] ERR.003.015.0003: JDBCPlatform Program Error, unable to create platform. 6 [IllegalArgumentException] -- 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, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (TEIID-444) Expose the cache to connectors.

by John Doyle (JIRA)

Expose the cache to connectors. ------------------------------- Key: TEIID-444 URL: https://jira.jboss.org/jira/browse/TEIID-444 Project: Teiid Issue Type: Feature Request Components: Connector API Reporter: John Doyle Assignee: Ramesh Reddy The XML-Relational connectors have historically had their own cache. I'm modifying the connectors to use JBoss cache and it would benefit users if this connector and other connectors with need of a cache could use the teiid cache to ease cache configuration and monitoring. -- 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, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIID-393) The Salesforce connector must be able to query about deleted SF objects.

by John Doyle (JIRA)

The Salesforce connector must be able to query about deleted SF objects. ------------------------------------------------------------------------ Key: TEIID-393 URL: https://jira.jboss.org/jira/browse/TEIID-393 Project: Teiid Issue Type: Feature Request Components: Salesforce Connector Reporter: John Doyle Assignee: John Doyle In order to make staging a local copy of SF data a viable solution, a customer has requested that the connector be able to report on deleted SF objects. The getDeleted cals in the SF API exists for this purpose. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-442) Simplify configuration mechanics

by Steven Hawkins (JIRA)

Simplify configuration mechanics -------------------------------- Key: TEIID-442 URL: https://jira.jboss.org/jira/browse/TEIID-442 Project: Teiid Issue Type: Task Components: Common, Console, Server Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 6.1.0 The current differentiation between start up and next startup is tenuous. After talking with Van and Ramesh a better simplified approach is to have a single live configuration, which essentially removes the notion of a startup configuration. As configuration changes are made, TEIID-441 will do a better job of informing the admin what should be restarted. When a host controller is asked to start processes it will save the current state of the configuration to the filesystem. And instead of keeping a single backup, we'll keep some rotating number of them. -- 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

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-443) Failure in JGroups Communication

by Ramesh Reddy (JIRA)

Failure in JGroups Communication -------------------------------- Key: TEIID-443 URL: https://jira.jboss.org/jira/browse/TEIID-443 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.1.0 ERROR Incoming-2,teiid,10.15.208.35:47163 org.jgroups.protocols.pbcast.NAKACK - failed reading retransmitted message java.io.IOException: failed reading header at org.jgroups.Message.readHeader(Message.java:787) at org.jgroups.Message.readFrom(Message.java:673) at org.jgroups.util.Util.byteBufferToMessage(Util.java:808) at org.jgroups.protocols.pbcast.NAKACK.handleXmitRsp(NAKACK.java:1038) at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:709) at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167) at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:308) at org.jgroups.protocols.MERGE2.up(MERGE2.java:144) at org.jgroups.protocols.Discovery.up(Discovery.java:263) at org.jgroups.protocols.TP.passMessageUp(TP.java:1275) at org.jgroups.protocols.TP.access$100(TP.java:49) at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1818) at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1797) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.InstantiationException: com.metamatrix.common.messaging.jgroups.JGroupsMessageBus$FederateHeader at java.lang.Class.newInstance0(Class.java:340) at java.lang.Class.newInstance(Class.java:308) at org.jgroups.Message.readHeader(Message.java:777) -- 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

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2009