March 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Closed: (TEIID-373) MMx Audit logs may contain extremely long lines that are essentially unviewable

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-373?page=com.atlassian.jira.plugin.... ] Steven Hawkins closed TEIID-373. -------------------------------- > MMx Audit logs may contain extremely long lines that are essentially unviewable > ------------------------------------------------------------------------------- > > Key: TEIID-373 > URL: https://issues.jboss.org/browse/TEIID-373 > Project: Teiid > Issue Type: Task > Components: Embedded, Server > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Paul Nittel > Priority: Minor > Attachments: MyAudit.zip > > > I'm attaching an example of an audit log that has a really long line that, maybe, has carriage returns without linefeeds. Regardless, the resulting file is illegible by Linux text editors. I tried with gedit and the text editor in Eclipse. Neither could display the file in reasonable fashion. > Windows fares better, but it's no picnic. > The contents of the audit log are from setting up a data role for reading the tables in MMR. 2.2MB as a result! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-846) Capabilities are not checked for insert update delete

by Steven Hawkins (JIRA)

Capabilities are not checked for insert update delete ----------------------------------------------------- Key: TEIID-846 URL: https://jira.jboss.org/jira/browse/TEIID-846 Project: Teiid Issue Type: Bug Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Capabilities are not checked for insert update delete operations, the original expectation was probably that the connector will throw an exception on an unsupported construct. However most connectors aren't written to properly handle unsupported pushdown sql. -- 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

13 years, 9 months

1
3
0 / 0

[JBoss JIRA] Closed: (TEIID-146) Translate Criteria enhancement

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-146?page=com.atlassian.jira.plugin.... ] Steven Hawkins closed TEIID-146. -------------------------------- > Translate Criteria enhancement > ------------------------------ > > Key: TEIID-146 > URL: https://issues.jboss.org/browse/TEIID-146 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 9.x > Reporter: Li Liang > Priority: Optional > Fix For: 7.3 > > > This is related to case 6658. There are limitations when using Translate Criteria: > 1. Alias is not handled. > 2. If the following query is used to define select query, although a.c and b.c are equivalent, use Translate Criteria on b does not work. > select a.c from a, b where a.c=b.c -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1335) Customer requesting the ability to make query planner always create dependent joins.

by Debbie Steigner (JIRA)

Customer requesting the ability to make query planner always create dependent joins. ------------------------------------------------------------------------------------ Key: TEIID-1335 URL: https://jira.jboss.org/browse/TEIID-1335 Project: Teiid Issue Type: Feature Request Components: Server Reporter: Debbie Steigner Assignee: Steven Hawkins Nike is finding that the query planner often chooses to use a non-dependent join plan, even when cost statistics have been gathered on all source systems and a dependent plan would perform much better. I've showed them how to use option makedep to force a dependent join scenario. However, it requires careful analysis of each query to setup the proper makedep parameters, and may not be feasible when working with hibernate as the client. Thus, they ask: is there any way to tell the query planner to always use dependent join for every join, no matter what. -- 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

13 years, 9 months

2
4
0 / 0

[JBoss JIRA] Closed: (TEIID-1369) ModeShape jdbc driver is returning jdcr_path column, but the teiid modeshape translator is looking for mode_path. The translator should be changed to look for jcr_path.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1369?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1369. --------------------------------- > ModeShape jdbc driver is returning jdcr_path column, but the teiid modeshape translator is looking for mode_path. The translator should be changed to look for jcr_path. > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1369 > URL: https://issues.jboss.org/browse/TEIID-1369 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.1.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 7.1.1 > > > The Teiid Modeshape translator needs to be changed to look for the jcr_path column, instead of mode_path. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-1380) When server is shut down, and then a vdb is replaced in the deploy directory, the teiid metadata cache becomes out of sync, and requires the user to delete the <server>data/teiid directory

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1380?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1380. --------------------------------- > When server is shut down, and then a vdb is replaced in the deploy directory, the teiid metadata cache becomes out of sync, and requires the user to delete the <server>data/teiid directory > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1380 > URL: https://issues.jboss.org/browse/TEIID-1380 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > > If a vdb is replaced while the server is shut down, the teiid metadata cache can become out-of-sync and the to fix it, the <server>data/teiid directory must be deleted to force it to refresh and sync up. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1385) Add a way to support escaped strings

by Steven Hawkins (JIRA)

Add a way to support escaped strings ------------------------------------ Key: TEIID-1385 URL: https://jira.jboss.org/browse/TEIID-1385 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.3 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.3 We should have either an string literal escape E '..' such as PostgreSQL or an escape function that can handle standard escape sequences. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1324) Deploy JOPR Plugin on JON/RHQ

by Cristiano Nicolai (JIRA)

Deploy JOPR Plugin on JON/RHQ ----------------------------- Key: TEIID-1324 URL: https://jira.jboss.org/browse/TEIID-1324 Project: Teiid Issue Type: Bug Components: Jopr Plugin Affects Versions: 7.2 Environment: Jboss EAP 5.1, JON 2.4, jon-plugin-pack-eap-2.4.0.GA Reporter: Cristiano Nicolai Assignee: Steven Hawkins When deploying Teiid JOPR plugin on JON, when the agent try to run the plugin there are some missing classes. Caused by: java.lang.NoClassDefFoundError: org/jboss/reflect/spi/TypeInfo at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) at java.lang.Class.getConstructor0(Class.java:2699) at java.lang.Class.newInstance0(Class.java:326) at java.lang.Class.newInstance(Class.java:308) at org.jboss.metatype.plugins.values.MetaValueFactoryBuilder$1.run(MetaValueFactoryBuilder.java:71) at org.jboss.metatype.plugins.values.MetaValueFactoryBuilder$1.run(MetaValueFactoryBuilder.java:46) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.metatype.plugins.values.MetaValueFactoryBuilder.<clinit>(MetaValueFactoryBuilder.java:45) at org.jboss.metatype.api.values.MetaValueFactory.<clinit>(MetaValueFactory.java:41) at org.teiid.rhq.admin.DQPManagementView.<clinit>(DQPManagementView.java:68) at org.teiid.rhq.plugin.VDBComponent.getAvailability(VDBComponent.java:139) at sun.reflect.GeneratedMethodAccessor50.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525) ... 5 more Basically the missing jar is jboss-metatype.jar. I tried some classloader configuration including the missing jar in teiid-console-7.2.0.Beta1.jar/lib, but as it has dependent classes (jboss-managed.jar) that are loaded in jboss-as-5 RHQ plugin I couldn't find any solution without changing the jboss-as-5 code. Probably some sync with RHQ guys is needed because jboss-managed.jar depends on jboss-metatype.jar. My workaround for this was a code change in ApplicationServerDiscoveryComponent to include the required jar from the AS installation. private static final List<String> CLIENT_JARS = Arrays.asList( // NOTE: The jbossall-client.jar aggregates a whole bunch of other jars from the client dir via its // MANIFEST.MF Class-Path. "client/jbossall-client.jar", "client/trove.jar", "client/javassist.jar", "common/lib/jboss-security-aspects.jar", "lib/jboss-managed.jar", "lib/jboss-metatype.jar", "lib/jboss-reflect.jar", "lib/jboss-dependency.jar" ); Fixing this class dependency the plugin start to require some Teiid client classes and to solve this I just copy the teiid-7.2.0.Beta1-client.jar to teiid-console-7.2.0.Beta1.jar/lib and redeploy the plugin. -- 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

13 years, 9 months

4
15
0 / 0

[JBoss JIRA] Created: (TEIID-1396) XML_PLAN output to server log too verbose for DEBUG level logging

by Paul Nittel (JIRA)

XML_PLAN output to server log too verbose for DEBUG level logging ----------------------------------------------------------------- Key: TEIID-1396 URL: https://issues.jboss.org/browse/TEIID-1396 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1.1 Environment: RHEL 5, SOA-P 5.1 ER5, JBDS 4.0 Beta2 (H33) Reporter: Paul Nittel Assignee: Steven Hawkins I was executing the E2E Staging Table test script and executed a query of the XML document from Designer. It took a long time--longer than I'd anticipated--so I looked at the server log to see what had happened. Turns out the server log had grown to 1.2GB in roughly 10 minutes. Checking the log (carefully!) I found XML_PLAN entries accounted for 8,759,795 lines of the 10,267,566 line log file. A sample of the entries look like: 2010-12-14 10:01:47,612 DEBUG [org.teiid.PROCESSOR.XML_PLAN] (Worker28_QueryProcessorQueue599) [showState] currentObject: shows 2010-12-14 10:01:47,612 DEBUG [org.teiid.PROCESSOR.XML_PLAN] (Worker28_QueryProcessorQueue599) [showState] currentObject.getNillableDescriptor(): null 2010-12-14 10:01:47,612 DEBUG [org.teiid.PROCESSOR.XML_PLAN] (Worker28_QueryProcessorQueue599) [showState] workingElements: [programId, programName, rating] 2010-12-14 10:01:47,613 DEBUG [org.teiid.PROCESSOR.XML_PLAN] (Worker28_QueryProcessorQueue599) [showState] currentParent.getParent(): ResultSet 2010-12-14 10:01:47,613 DEBUG [org.teiid.PROCESSOR.XML_PLAN] (Worker28_QueryProcessorQueue599) Executing instruction NEXT TVDOC.TVGUIDEROOTALL.MAPPINGCLASSES.SHOWS_1 2010-12-14 10:01:47,613 DEBUG [org.teiid.PROCESSOR.XML_PLAN] (Worker28_QueryProcessorQueue599) NEXT TVDOC.TVGUIDEROOTALL.MAPPINGCLASSES.SHOWS_1 2010-12-14 10:01:47,613 DEBUG [org.teiid.PROCESSOR.XML_PLAN] (Worker28_QueryProcessorQueue599) Processor Environment popped program w/ recursion count 0 ; 2 programs left. 2010-12-14 10:01:47,613 DEBUG [org.teiid.PROCESSOR.XML_PLAN] (Worker28_QueryProcessorQueue599) Executing instruction LOOP TVDOC.TVGUIDEROOTALL.MAPPINGCLASSES.SHOWS_1 2010-12-14 10:01:47,613 DEBUG [org.teiid.PROCESSOR.XML_PLAN] (Worker28_QueryProcessorQueue599) WHILE repeating for result set: TVDOC.TVGUIDEROOTALL.MAPPINGCLASSES.SHOWS_1 , block program: PROGRAM size 7 2010-12-14 10:01:47,613 DEBUG [org.teiid.PROCESSOR.XML_PLAN] (Worker28_QueryProcessorQueue599) Pushed non-recursive program w/ recursion count 0 2010-12-14 10:01:47,613 DEBUG [org.teiid.PROCESSOR.XML_PLAN] (Worker28_QueryProcessorQueue599) Executing instruction ELEM shows (namespaces ) 2010-12-14 10:01:47,613 DEBUG [org.teiid.PROCESSOR.XML_PLAN] (Worker28_QueryProcessorQueue599) [showState] State Vars at: addElement(2) - TOP 2010-12-14 10:01:47,613 DEBUG [org.teiid.PROCESSOR.XML_PLAN] (Worker28_QueryProcessorQueue599) [showState] currentParent: producer 2010-12-14 10:01:47,613 DEBUG [org.teiid.PROCESSOR.XML_PLAN] (Worker28_QueryProcessorQueue599) [showState] currentObject: shows 2010-12-14 10:01:47,613 DEBUG [org.teiid.PROCESSOR.XML_PLAN] (Worker28_QueryProcessorQueue599) [showState] currentObject.getNillableDescriptor(): null Speaking with Ramesh, he suggests possibly moving this type of output to TRACE. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1351) Replace translate criteria

by Steven Hawkins (JIRA)

Replace translate criteria -------------------------- Key: TEIID-1351 URL: https://jira.jboss.org/browse/TEIID-1351 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.3 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 7.3 While we hardened the usage in 7.2, translate criteria has too many implied restrictions to reliably perform the update/delete the user query is specifying. It would be better to rely on better default handling (especially pass-through) TEIID-1349 and to remove the current restrictions on virtual update, such as requiring scalar set clause values and no subquery evaluation TEIID-1276. This change should not remove the possibility of using TRANSLATE CRITERIA/CREATE PROCEDURE, as it will not be removed until Teiid 8 or later. Beyond the default handling, one possible construct is to provide the user with an cursor that contains the update (or delete) set with the corresponding updated values. Then leave it up to the user to iterate over the change set and process the changes. One drawback with this approach is that it may be hard to decipher from the view output rows how to apply the updates to constituent tables when the view transformation is a set or join and branch descriminators or additional primary keys are not projected. Of course those situations were already difficult to handle with translate criteria. This will require coordinated designer changes. -- 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

13 years, 9 months

1
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2011