October 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2267) Verify Custom Appenders (command, audit) work in AS7

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2267: ----------------------------------- Summary: Verify Custom Appenders (command, audit) work in AS7 Key: TEIID-2267 URL: https://issues.jboss.org/browse/TEIID-2267 Project: Teiid Issue Type: Task Components: Common Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.2 AS7 has different logging configuration than the AS 5.1. The appenders do work as is, and configuration may be different. However based on this AS7-4925 it looks like Log4J appender can be supported in AS 7.2. This information needs to be verified and update Teiid documentation at https://docs.jboss.org/author/display/teiid/Custom+Logging https://docs.jboss.org/author/display/teiid/Logging Since 7.2, is not available yet if we want to fix this change the document to use java.util.logging.Handler interface to extend and add configuration like below in the logging subsystem in standalone-teiid.xml file {code} <custom-handler name="COMMAND" module="" class="org.something.CustomAppender"> </custom-handler> <logger category="org.teiid.COMMAND_LOG"> <level name="INFO"/> <handler name="COMMAND"/> </logger> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
4
0 / 0

[JBoss JIRA] (TEIID-2266) When using JNDI to obtain cache, need to support EmbeddedCacheManager

by Van Halbert (JIRA)

Van Halbert created TEIID-2266: ---------------------------------- Summary: When using JNDI to obtain cache, need to support EmbeddedCacheManager Key: TEIID-2266 URL: https://issues.jboss.org/browse/TEIID-2266 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.2 Reporter: Van Halbert Assignee: Van Halbert When building the quick start for infinispan, the test application is using the following injection: <code> @Produces @Resource(lookup = "java:jboss/infinispan/container/teiid-infinispan-quickstart") private CacheContainer container; </code> But when the Infinispan connector tries to get the container from JNDI, getting a ClassCastException: org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager cannot be cast to org.infinispan.api.BasicCacheContainer So the injection must be handling getting the container, for which wasn't taken into consideration. So the connector-infinispan needs to be changed accordingly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
4
0 / 0

[JBoss JIRA] (TEIID-2193) System Catalog queries producing IllegalArgumentException: Invalid Type

by Warren Gibson (JIRA)

Warren Gibson created TEIID-2193: ------------------------------------ Summary: System Catalog queries producing IllegalArgumentException: Invalid Type Key: TEIID-2193 URL: https://issues.jboss.org/browse/TEIID-2193 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.1 Environment: Teiid 8.1 with AS 7.1.1 Reporter: Warren Gibson Assignee: Steven Hawkins All System Catalog queries producing IllegalArgumentException: Invalid Type Example queries: select * from SYS.VirtualDatabases select VDBName, SchemaName, Name, Type, NameInSource, IsPhysical, SupportsUpdates, UID, Cardinality, Description, IsSystem, IsMaterialized from SYS.Tables 09:50:55,300 DEBUG [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue12) Request Thread FwKHlqK21Snf.6 - error occurred: java.lang.IllegalArgumentException: Invalid type: org.teiid.metadata.Schema. at org.teiid.query.metadata.TransformationMetadata.createInvalidRecordTypeException(TransformationMetadata.java:619) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.metadata.TransformationMetadata.getModelID(TransformationMetadata.java:253) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.metadata.TempMetadataAdapter.getModelID(TempMetadataAdapter.java:175) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.metadata.TempMetadataAdapter.getModelID(TempMetadataAdapter.java:175) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.optimizer.relational.plantree.PlanNode.recordDebugAnnotation(PlanNode.java:423) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.optimizer.relational.rules.RulePushLimit.raiseAccessOverLimit(RulePushLimit.java:235) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.optimizer.relational.rules.RuleRaiseAccess.raiseAccessNode(RuleRaiseAccess.java:293) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.optimizer.relational.rules.RuleRaiseAccess.execute(RuleRaiseAccess.java:76) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:457) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:199) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:188) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:433) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.Request.processRequest(Request.java:453) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:532) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:280) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:219) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:249) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.1.0.Final.jar:8.1.0.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
5
0 / 0

[JBoss JIRA] (TEIID-2191) Detect recursive view definitions

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2191: ------------------------------------- Summary: Detect recursive view definitions Key: TEIID-2191 URL: https://issues.jboss.org/browse/TEIID-2191 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.2 A feature from designer that was never added to the runtime is detection of recursive view definitions. Currently if a recursive view is supplied via ddl or translator it will cause a stackoverflow in the relational planner when it is accessed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
3
0 / 0

[JBoss JIRA] (TEIID-2196) The clearCache method (adminShell) which accepts the VDB name should verify the VDB name and report if not found

by Paul Nittel (JIRA)

Paul Nittel created TEIID-2196: ---------------------------------- Summary: The clearCache method (adminShell) which accepts the VDB name should verify the VDB name and report if not found Key: TEIID-2196 URL: https://issues.jboss.org/browse/TEIID-2196 Project: Teiid Issue Type: Enhancement Components: AdminApi Affects Versions: 7.7.1 Reporter: Paul Nittel Assignee: Steven Hawkins Priority: Minor Fix For: 8.2 The clearCache(type, vdb, vdb-version) should report when the VDB and version specified does not exist. Presently (version 7.7.1/EDS 5.3) it appears to have been successful, even if the VDB name specified is a wildcard character. As an example, no exception was thrown for this: clearCache("PREPARED_PLAN_CACHE","*",1) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
5
0 / 0

[JBoss JIRA] (TEIID-2239) ddl parsing should have built-in prefixes for teiid namespaces

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2239: ------------------------------------- Summary: ddl parsing should have built-in prefixes for teiid namespaces Key: TEIID-2239 URL: https://issues.jboss.org/browse/TEIID-2239 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.2 It's cumbersome to type out the uri prefix for relational or sf entries. There should be well-known prefixes already defined. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
2
0 / 0

[JBoss JIRA] (TEIID-2264) Parameter replacement for an update statement is not happening for set clause.

by Vineela Gampa (JIRA)

Vineela Gampa created TEIID-2264: ------------------------------------ Summary: Parameter replacement for an update statement is not happening for set clause. Key: TEIID-2264 URL: https://issues.jboss.org/browse/TEIID-2264 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 8.1 Reporter: Vineela Gampa Assignee: Steven Hawkins -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
7
0 / 0

[JBoss JIRA] (TEIID-2238) Provide a means of seeing the generated default update/insert/delete procedure transformations

by Paul Nittel (JIRA)

Paul Nittel created TEIID-2238: ---------------------------------- Summary: Provide a means of seeing the generated default update/insert/delete procedure transformations Key: TEIID-2238 URL: https://issues.jboss.org/browse/TEIID-2238 Project: Teiid Issue Type: Enhancement Affects Versions: 7.7.1 Environment: JBDS 5 GA with EDS Reporter: Paul Nittel Assignee: Steven Hawkins Priority: Minor When a transformation supports updates and defaults are created for Insert, Update, and Delete procedures it would be handy to show what was generated. The user could them modify that starting poin--or even the SELECT--to better suit their needs. It might help them understand messages like: WARNING: The updatable view query has a non key preserving group PartsOracle.STATUS, which cannot be targeted by INSERT/UPDATE/DELETE operations. In this instance, the SELECT query is: SELECT * FROM PartsOracle.STATUS, PartsOracle.SUPPLIER WHERE PartsOracle.STATUS.STATUS_ID = PartsOracle.SUPPLIER.SUPPLIER_STATUS -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
3
0 / 0

[JBoss JIRA] (TEIID-2283) Failure to create LDAP connection

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2283: ----------------------------------- Summary: Failure to create LDAP connection Key: TEIID-2283 URL: https://issues.jboss.org/browse/TEIID-2283 Project: Teiid Issue Type: Bug Components: LDAP Connector Affects Versions: 8.1, 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.2 Trying to make connection to LDAP is resulting in the following exception {code} .ResourceException: Initializing LDAP directory context failed. Please check LDAP connection properties, including username and password: JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "org.jboss.teiid:main" from local module loader @9ba6076 (roots: /home/rareddy/testing/jboss-as-7.1.1.Final/modules) at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.initializeLDAPContext(LDAPConnectionImpl.java:138) at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.<init>(LDAPConnectionImpl.java:73) at org.teiid.resource.adapter.ldap.LDAPManagedConnectionFactory$1.getConnection(LDAPManagedConnectionFactory.java:46) at org.teiid.resource.adapter.ldap.LDAPManagedConnectionFactory$1.getConnection(LDAPManagedConnectionFactory.java:43) at org.teiid.resource.spi.BasicManagedConnectionFactory.createManagedConnection(BasicManagedConnectionFactory.java:70) [teiid-api-8.2.0.CR1-SNAPSHOT.jar:8.2.0.CR1-SNAPSHOT] at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:761) [ironjacamar-core-impl-1.0.9.Final.jar:1.0.9.Final] at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:343) [ironjacamar-core-impl-1.0.9.Final.jar:1.0.9.Final] {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[JBoss JIRA] (TEIID-2227) Add support for a return statement

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2227: ------------------------------------- Summary: Add support for a return statement Key: TEIID-2227 URL: https://issues.jboss.org/browse/TEIID-2227 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins In many situations it would be convenient to have a return statement in the procedure language. It could optionally support a return value for procedures returning scalar values. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2012