February 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1692) Include an example of the LOOKUP function in the Ref Guide

by Paul Nittel (JIRA)

Include an example of the LOOKUP function in the Ref Guide ---------------------------------------------------------- Key: TEIID-1692 URL: https://issues.jboss.org/browse/TEIID-1692 Project: Teiid Issue Type: Feature Request Components: Documentation Affects Versions: 7.4 Environment: All Reporter: Paul Nittel Assignee: Steven Hawkins Once again I confused myself while trying to use the LOOKUP function. The first three arguments are all quoted strings. A simple example might help demonstrate this to the reader. I believe this may work as it follows the descriptive text. SELECT LOOKUP('ModelName.StatePostalCodes', 'StateDisplayName', 'PostalCode', Table.WhatStateMatchesThisPostalCode) AS LookedUpStateName FROM Table -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIID-1689) Load internal mateirlized view cached contents when node joins the cluster

by Ramesh Reddy (JIRA)

Load internal mateirlized view cached contents when node joins the cluster -------------------------------------------------------------------------- Key: TEIID-1689 URL: https://issues.jboss.org/browse/TEIID-1689 Project: Teiid Issue Type: Feature Request Components: Server Affects Versions: 7.4.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy When IMV loaded at Node 1, and the contents of the that IMV will be loaded at Node 2 only when the query is issued against it. Then user incurs the wait time to load the contents from Node 1. If in the situation if Node 1, went down before the query to Node 2, in that case node 2 has to fetch from the source and cached contents will be lost. This can be avoided by hot loading the all the cached contents at the start of the node from other nodes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
5
0 / 0

[JBoss JIRA] (TEIID-1711) Unify logger definitions used in SOA-P and Teiid

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1711?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1711. --------------------------------- > Unify logger definitions used in SOA-P and Teiid > ------------------------------------------------ > > Key: TEIID-1711 > URL: https://issues.jboss.org/browse/TEIID-1711 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 7.4.1 > Reporter: Boris Belovic > Assignee: Van Halbert > Priority: Minor > Fix For: 7.4.1 > > > Main LOG4J config file - jboss-log4j.xml - uses <category> elements for logger definition, Teiid comes with newer <logger> elements for particular logger definition. If customer installs Teiid into SOA-P then he gets two different logger definitions in jboss-log4j.xml - LOG4J config file contains both <category> and <logger> elements. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1691) Improve xml staging table planning

by Steven Hawkins (JIRA)

Improve xml staging table planning ---------------------------------- Key: TEIID-1691 URL: https://issues.jboss.org/browse/TEIID-1691 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 7.4.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4.1, 7.5 Staging table planning should allow for dependent join loads using the parent values. This should be done regardless of whether the parent is also staged. For large staged tables it would also be good to index on the join columns. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
2
0 / 0

[JBoss JIRA] (TEIID-1860) add m2e entries in .pom files to remove errors indicated by Eclipse and the m2e plugin

by Johnathon Lee (Created) (JIRA)

add m2e entries in .pom files to remove errors indicated by Eclipse and the m2e plugin -------------------------------------------------------------------------------------- Key: TEIID-1860 URL: https://issues.jboss.org/browse/TEIID-1860 Project: Teiid Issue Type: Enhancement Components: AdminApi, Common, Connector API, Query Engine, Server Affects Versions: 7.6 Environment: Eclipse IDE, Teiid Reporter: Johnathon Lee Assignee: Steven Hawkins Attachments: m2eCompat.patch When using Eclipse Indigo and and the m2e plugin, plugin Management must be aware of how to handle maven lifecycle events. The attached patch tells the offending events to be ignored. This does not affect the actual mvn commands ran outside of the IDE. -- 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

12 years, 3 months

6
5
0 / 0

[JBoss JIRA] Created: (TEIID-1727) Undeploying a vdb inappropriately updates all vdbs

by Steven Hawkins (JIRA)

Undeploying a vdb inappropriately updates all vdbs -------------------------------------------------- Key: TEIID-1727 URL: https://issues.jboss.org/browse/TEIID-1727 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4.1, 7.6 When a vdb is undeployed the VDBRepository.removeVDB logic unconditionally calls removeChild on all vdbs in the repository. This causes each to build a new metadata state resulting in duplicate mat views and inconsistent metadata updates. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1615) Add features to support relate planning

by Steven Hawkins (JIRA)

Add features to support relate planning --------------------------------------- Key: TEIID-1615 URL: https://issues.jboss.org/browse/TEIID-1615 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4.1 MetaMatrix had an xml relate planner feature that can be reproduced with standard xml processing with additional features. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
7
0 / 0

[JBoss JIRA] (TEIID-1660) EDS BQT Queries failing on SqlServer 2005 with SQLServerException "Type DATE is not a defined system type"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1660?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1660. --------------------------------- > EDS BQT Queries failing on SqlServer 2005 with SQLServerException "Type DATE is not a defined system type" > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-1660 > URL: https://issues.jboss.org/browse/TEIID-1660 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4.1 > Reporter: Warren Gibson > Assignee: Steven Hawkins > Fix For: 7.4.1, 7.5 > > > 17 EDS BQT queries are failing when using SqlServer 2005 as a source. SQLServerException "Type DATE is not a defined system type". Below is an example. They are passing in SqlServer 2008. VDB is attached. > Query: SELECT BQT1.SmallA.IntKey FROM BQT1.SmallA WHERE BQT1.SmallA.DateValue IN (convert('2000-01-12', date), convert('2000-02-02', date)) ORDER BY IntKey > Log: > 2011-06-28 10:35:18,130 DEBUG [org.teiid.CONNECTOR] (Worker16_QueryProcessorQueue136) Source-specific command: SELECT TOP 100 cast(g_0.IntKey AS int) AS c_0 FROM SmallA g_0 WHERE cast(replace(convert(varchar, g_0.DateValue, 102), '.', '-') AS datetime) IN (CAST('2000-01-12' AS DATE), CAST('2000-02-02' AS DATE)) ORDER BY c_0 > 2011-06-28 10:35:18,179 DEBUG [org.teiid.COMMAND_LOG] (Worker16_QueryProcessorQueue136) ERROR SRC COMMAND: endTime=2011-06-28 10:35:18.179 requestID=Q0JsTZlYNGm0.23 sourceCommandID=1 txID=null modelName=Source connectorBindingName=sqlserver sessionID=Q0JsTZlYNGm0 principal=user@teiid-security finalRowCount=null > 2011-06-28 10:35:18,179 WARN [org.teiid.CONNECTOR] (Worker16_QueryProcessorQueue136) Connector worker process failed for atomic-request=Q0JsTZlYNGm0.23.1.21 > [JDBCExecutionException] 243: Error Code:243 Message:'Type DATE is not a defined system type.' error executing statement(s): [Prepared Values: [] SQL: SELECT TOP 100 cast(g_0.IntKey AS int) AS c_0 FROM SmallA g_0 WHERE cast(replace(convert(varchar, g_0.DateValue, 102), '.', '-') AS datetime) IN (CAST('2000-01-12' AS DATE), CAST('2000-02-02' AS DATE)) ORDER BY c_0] > 1 [SQLServerException]Type DATE is not a defined system type. > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:90) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:264) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:338) > at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:80) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:138) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:135) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:197) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:636) > Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Type DATE is not a defined system type. > at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:196) > at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1454) > at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:388) > at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:338) > at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4026) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1416) > at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:185) > at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:160) > at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:281) > at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:342) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:86) > ... 13 more -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1681) Limit not working as expected

by Gaurav Chaudhary (JIRA)

Limit not working as expected ----------------------------- Key: TEIID-1681 URL: https://issues.jboss.org/browse/TEIID-1681 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.3 Reporter: Gaurav Chaudhary Assignee: Steven Hawkins select CHORUS_B."ID", CHORUS_B."ACCESS_MODE", CHORUS_B."USER_ID", CHORUS_B."CREATED_ON", CHORUS_B."NOTE",'chorusdata.note' as "__objecttype__" from (select * from chorus_notes.RETRIEVE_NOTES where OBJECT_PKEY = xmlserialize(xmlelement("demodata.rule", XMLATTRIBUTES(cast('name 1' as String) as "name",cast('sysid 0' as String) as "system",cast('user 1000' as String) as "user")) as String)) as CHORUS_B LIMIT 50 This query is not returning correct results unless we remove Limit from this. If we include Limit over here, it interchanges the columns and returning incorrect data. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
6
0 / 0

[JBoss JIRA] (TEIID-1847) Salesforce connector does not report UnexpectedErrorFault exceptions correctly when calling getUpdated

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1847?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1847. --------------------------------- > Salesforce connector does not report UnexpectedErrorFault exceptions correctly when calling getUpdated > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-1847 > URL: https://issues.jboss.org/browse/TEIID-1847 > Project: Teiid > Issue Type: Quality Risk > Components: Salesforce Connector > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Minor > Labels: salesforce > > When encountering an UnexpectedErrorFault with com.sforce.soap.partner.SoapBindingStub.GetUpdated(), com.metamatrix.connector.salesforce.connection.SalesforceConnection.getUpdated() throws a null error message instead of the message returned from Salesforce. It appears that the getUpdated() method is using java.rmi.RemoteException.getMessage() when it should be using SFDC com.sforce.soap.partner.fault.ApiFault.getExceptionMessage() for "UnexpectedErrorFault" exceptions. Associated stack trace below. > [Salesforce Connector_1246|9725_Worker_106|0] ERROR <CONNECTOR|0> Connector worker process failed for atomic-request=5707647.13.7.333713 > ConnectorException: Status ERROR: com.metamatrix.core code=0 null > at com.metamatrix.connector.salesforce.connection.SalesforceConnection.getUpdated(SalesforceConnection.java:737) > at com.metamatrix.connector.salesforce.execution.GetUpdatedExecutionImpl.execute(GetUpdatedExecutionImpl.java:65) > at com.metamatrix.connector.salesforce.execution.ProcedureExecutionParentImpl.execute(ProcedureExecutionParentImpl.java:86) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processNewRequest(ConnectorWorker.java:275) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.process(ConnectorWorker.java:141) > at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:64) -- 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

12 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2012