October 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1230) TeiidDriver is used instead of MetaMatrixDriver during connection to the MM Server

by Warren Gibson (JIRA)

TeiidDriver is used instead of MetaMatrixDriver during connection to the MM Server ---------------------------------------------------------------------------------- Key: TEIID-1230 URL: https://jira.jboss.org/browse/TEIID-1230 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.1 Reporter: Warren Gibson Assignee: Steve Hawkins Fix For: 7.1 The URL from MM is supported in the Teiid, thus MM Driver fails to load if this is not available in the DriverManager driver order. Log attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-1322) Stored procedures are not pre-evaluating scalar subquery arguments.

by Steven Hawkins (JIRA)

Stored procedures are not pre-evaluating scalar subquery arguments. ------------------------------------------------------------------- Key: TEIID-1322 URL: https://jira.jboss.org/browse/TEIID-1322 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 Our current code is not pre-evaluating scalar subqueries used as arguments to stored procedures. This should have started working in 6.x. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1315) Teiid misinterprets relative location of XSD when doc model is in different folder: causes Unknown Query Metadata error

by Paul Nittel (JIRA)

Teiid misinterprets relative location of XSD when doc model is in different folder: causes Unknown Query Metadata error ----------------------------------------------------------------------------------------------------------------------- Key: TEIID-1315 URL: https://jira.jboss.org/browse/TEIID-1315 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1.1 Environment: SOA-P ER3, JBDS 4.0.0 Beta 1 Reporter: Paul Nittel Assignee: Steven Hawkins Fix For: 7.1.1 I executed E2eAudioBooksVdbExecutionTestScript_Teiid7 and found I could not query the BookSetMixed document. I received an exception which referred to "Unknown Query Metadata". The test calls for refactoring the models into various folders and the XML doc model winds up in <proj>/View/XMLDocuments. The XML Schemas are in <proj>/Source/XMLSchemas. In the VDB's index file for the XML document model, the path to the XSD is, for example: ../../Source/XmlSchemas/BookDatatypes.xsd. The query engine is not treating this as a file system, however, and is unable to locate the XSD. We refactored the XML document into the same fodler as the XSDs and the query then worked. I'll attach some artifacts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1276) Updating an existing VDB via copy-paste in the filesystem causes ConcurrentModificationException

by John Doyle (JIRA)

Updating an existing VDB via copy-paste in the filesystem causes ConcurrentModificationException ------------------------------------------------------------------------------------------------ Key: TEIID-1276 URL: https://jira.jboss.org/browse/TEIID-1276 Project: Teiid Issue Type: Bug Affects Versions: 7.1.1 Reporter: John Doyle Assignee: Steven Hawkins If you have a vdb deployed in Teiid and deploy an updated version by pasting the VDB into the deploy directory, a ConcurrentModificationException is thrown. It appears that the original is undeployed, but the new one is not deployed. You cannot connect to the VDB after the exception. 11:51:12,223 INFO [RUNTIME] VDB "Lobs.1[OracleClobs[OracleClobs/oracle/OracleClobs]]" undeployed. 11:51:12,615 INFO [PROCESSOR] Clearing prepared plan cache 11:51:12,616 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/NotBackedUp/jdoyle/Teiid_955/jboss-5.1.0.GA/server/default/deploy/Lobs.vdb/ state=PreReal mode=Manual requiredState=Real org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/NotBackedUp/jdoyle/Teiid_955/jboss-5.1.0.GA/server/default/deploy/Lobs.vdb/ at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.util.ConcurrentModificationException at java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:373) at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:384) at org.teiid.dqp.internal.process.SessionAwareCache.clearCache(SessionAwareCache.java:185) at org.teiid.dqp.internal.process.SessionAwareCache.clearForVDB(SessionAwareCache.java:179) at org.teiid.dqp.internal.process.DQPCore.clearPlanCache(DQPCore.java:560) at org.teiid.dqp.internal.process.DQPCore.clearCache(DQPCore.java:612) at org.teiid.jboss.deployers.RuntimeEngineDeployer$1.added(RuntimeEngineDeployer.java:214) at org.teiid.deployers.VDBRepository.notifyAdd(VDBRepository.java:225) at org.teiid.deployers.VDBRepository.addVDB(VDBRepository.java:84) at org.teiid.deployers.VDBDeployer.deploy(VDBDeployer.java:145) at org.teiid.deployers.VDBDeployer.deploy(VDBDeployer.java:60) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) ... 24 more 11:51:12,619 WARN [HDScanner] Failed to process changes org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfszip:/NotBackedUp/jdoyle/Teiid_955/jboss-5.1.0.GA/server/default/deploy/Lobs.vdb/ -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/NotBackedUp/jdoyle/Teiid_955/jboss-5.1.0.GA/server/default/deploy/Lobs.vdb/ DEPLOYMENTS IN ERROR: Deployment "vfszip:/NotBackedUp/jdoyle/Teiid_955/jboss-5.1.0.GA/server/default/deploy/Lobs.vdb/" is in error due to the following reason(s): java.util.ConcurrentModificationException at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993) at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (TEIID-1294) procedure validation issues

by Steven Hawkins (JIRA)

procedure validation issues --------------------------- Key: TEIID-1294 URL: https://jira.jboss.org/browse/TEIID-1294 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 We should introduce several validations to ensure proper procedure usage. The first is to not allow the use of insert/update/delete as a command statement that creates the implicit return cursor. There may be others based upon TEIID-1237 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-1314) BigDecimal values truncated with jConnect 6.05

by Steven Hawkins (JIRA)

BigDecimal values truncated with jConnect 6.05 ---------------------------------------------- Key: TEIID-1314 URL: https://jira.jboss.org/browse/TEIID-1314 Project: Teiid Issue Type: Thirdparty Change Components: JDBC Connector Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 the setObject(pos, val, type) method appears to be calling setObject(pos, val, type, 0) where 0 is being picked up as the scale. This is causing BigDecimal values to be truncated. If we change the set method to setBigDecimal, then everything is fine and should work on the other driver types as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1313) Possible duplicate rows at when using nested table feature. When using TABLE or XMLTABLE or TEXTTABLE.

by Ramesh Reddy (JIRA)

Possible duplicate rows at when using nested table feature. When using TABLE or XMLTABLE or TEXTTABLE. ------------------------------------------------------------------------------------------------------ Key: TEIID-1313 URL: https://jira.jboss.org/browse/TEIID-1313 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Ramesh Reddy Assignee: Steven Hawkins Priority: Critical Fix For: 7.1.1 When using the XMLTable, or TextTable or TABLE semantics to use the Nested table reference http://docs.jboss.org/teiid/7.1.0.Final/reference/en-US/html_single/#nest..., with multiple batch (more than 512 rows) there could be a duplicate row at the beginning of the next batch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1319) Incorrect format for postgres timestamp to string

by Steven Hawkins (JIRA)

Incorrect format for postgres timestamp to string ------------------------------------------------- Key: TEIID-1319 URL: https://jira.jboss.org/browse/TEIID-1319 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 We should be using US, not UF for the microseconds. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1307) Client Dev Guide - repeated property in tables for Driver & Datasource

by Darrin Mison (JIRA)

Client Dev Guide - repeated property in tables for Driver & Datasource ---------------------------------------------------------------------- Key: TEIID-1307 URL: https://jira.jboss.org/browse/TEIID-1307 Project: Teiid Issue Type: Bug Components: Documentation Affects Versions: 7.1 Reporter: Darrin Mison Assignee: Steven Hawkins Section 1.2 suggests that all of the Driver URL properties are valid in for Datasource as well. The PassthroughAuthentication property is listed in both Table 1.2 and 1.1 with the same text. Is this property redundant in Table 1.2 or am I reading this wrong ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-1233) VDB version from the file name is not being picked up

by Steve Hawkins (JIRA)

VDB version from the file name is not being picked up ----------------------------------------------------- Key: TEIID-1233 URL: https://jira.jboss.org/browse/TEIID-1233 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Priority: Critical The version parsing logic is incorrect. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2010