August 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-829) revamp code table caching

by Steven Hawkins (JIRA)

revamp code table caching ------------------------- Key: TEIID-829 URL: https://jira.jboss.org/jira/browse/TEIID-829 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.3.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3.0 Code tables have several design issues: 1. the cache should allow for eviction and possibly expiration. 2. the cache should be backed by the common caching facility. 3. should allow for explicit scoping - at a minimum global vs. vdb, but additional may be good to allow session and request. 4. the implementation should be minimally blocking (in terms of both query execution and use of synchronization). -- 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

14 years, 4 months

2
8
0 / 0

[JBoss JIRA] Created: (TEIID-892) Add a capability to control bulk insert batch size

by Steven Hawkins (JIRA)

Add a capability to control bulk insert batch size -------------------------------------------------- Key: TEIID-892 URL: https://jira.jboss.org/jira/browse/TEIID-892 Project: Teiid Issue Type: Feature Request Components: Connector API, Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 7.0 Based upon a recent customer conversation our default batching strategy to the connector may not be the most performant for large datasets. In general our current approach limits batches to a maximum = processor batch size (default 2000). We already have a property connector batch size, but it's across all connectors - and is mostly irrelevant since the source fetch size will have a larger impact on performance and the result batches are resized to the processor batch size anyway. The only time connector batch size really matters is if we bring back "remote" connectors. -- 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

14 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1185) Shutting down JBoss AS server causes NPE in ClusterableCacheFactory

by Van Halbert (JIRA)

Shutting down JBoss AS server causes NPE in ClusterableCacheFactory ------------------------------------------------------------------- Key: TEIID-1185 URL: https://jira.jboss.org/browse/TEIID-1185 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.1 Environment: Jboss AS 5.1 Reporter: Van Halbert Assignee: Steve Hawkins Priority: Minor Start the Jboss AS server, open the admin console (not sure if this impacts it, but that was one of my steps), then shutdown the server, get this exception: 15:01:14,024 WARN [CreateDestroyLifecycleAction] Error during destroy for CacheFactory java.lang.NullPointerException at org.teiid.cache.jboss.ClusterableCacheFactory.destroy(ClusterableCacheFactory.java:66) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-1183) Cannot create a SalesForce datasource throught the admin API.

by John Doyle (JIRA)

Cannot create a SalesForce datasource throught the admin API. ------------------------------------------------------------- Key: TEIID-1183 URL: https://jira.jboss.org/browse/TEIID-1183 Project: Teiid Issue Type: Bug Components: Salesforce Connector Affects Versions: 7.1 Reporter: John Doyle Assignee: Steve Hawkins I'm able to create a salesforce ds.xml by hand, but cannot create one with the admin API. I'm attaching a sample java class with bugus username, password values. Here's the stack trace. org.teiid.templates.connector.RaXmlPropertyConverter.getRarProperties(RaXmlPropertyConverter.java:83), org.teiid.templates.connector.RaXmlPropertyConverter.getAsManagedProperties(RaXmlPropertyConverter.java:67), org.teiid.templates.connector.ConnectorTemplateInfo.populate(ConnectorTemplateInfo.java:75), org.teiid.templates.connector.ConnectorTemplateInfo.copy(ConnectorTemplateInfo.java:64), org.teiid.templates.connector.ConnectorTemplateInfo.copy(ConnectorTemplateInfo.java:44), org.jboss.profileservice.management.ManagementViewImpl.getTemplate(ManagementViewImpl.java:1334), org.teiid.adminapi.jboss.Admin.createDataSource(Admin.java:606), sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method), sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39), sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25), java.lang.reflect.Method.invoke(Method.java:597), org.teiid.logging.LogManager$LoggingProxy.invoke(LogManager.java:121), org.teiid.jboss.deployers.RuntimeEngineDeployer$1.invoke(RuntimeEngineDeployer.java:247), $Proxy261.createDataSource(Unknown Source), sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method), sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39), sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25), java.lang.reflect.Method.invoke(Method.java:597), org.teiid.transport.ServerWorkItem.run(ServerWorkItem.java:81), org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188), org.teiid.transport.SocketClientInstance.processMessagePacket(SocketClientInstance.java:160), org.teiid.transport.SocketClientInstance.receivedMessage(SocketClientInstance.java:149), org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:210), org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:100), org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545), org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754), org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:144), org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545), org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754), org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302), org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317), org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299), org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216), org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80), org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545), org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:540), org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274), org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261), org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:340), org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:272), org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:192), org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108), org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46), java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886), java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908), java.lang.Thread.run(Thread.java:619)] org.teiid.templates.connector.RaXmlPropertyConverter.getRarProperties(RaXmlPropertyConverter.java:83) org.teiid.templates.connector.RaXmlPropertyConverter.getAsManagedProperties(RaXmlPropertyConverter.java:67) org.teiid.templates.connector.ConnectorTemplateInfo.populate(ConnectorTemplateInfo.java:75) org.teiid.templates.connector.ConnectorTemplateInfo.copy(ConnectorTemplateInfo.java:64) org.teiid.templates.connector.ConnectorTemplateInfo.copy(ConnectorTemplateInfo.java:44) org.jboss.profileservice.management.ManagementViewImpl.getTemplate(ManagementViewImpl.java:1334) org.teiid.adminapi.jboss.Admin.createDataSource(Admin.java:606) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-1208) VDB "getStatus" through Admin API always returning "INACTIVE"

by Ramesh Reddy (JIRA)

VDB "getStatus" through Admin API always returning "INACTIVE" ------------------------------------------------------------- Key: TEIID-1208 URL: https://jira.jboss.org/browse/TEIID-1208 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 7.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1 When VDB status is queried through Admin API, it is always being returned as "INACTIVE", even though the VDB itself is active. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Closed: (TEIID-48) Better metadata for ODBC and materialization tables

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-48?page=com.atlassian.jira.plugin.sys... ] Steve Hawkins closed TEIID-48. ------------------------------ > Better metadata for ODBC and materialization tables > --------------------------------------------------- > > Key: TEIID-48 > URL: https://jira.jboss.org/browse/TEIID-48 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 7.0 > > > Materialization model and ODBC tables are currently visible in the metadata tree for all users. This is not desirable, but may be necessary since some clients should have that metadata. > At the very least we should be marking these as system tables. At best we would filter metadata based upon permissions. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1193) DB2 9.1 & 9.7 - VQT query SELECT * FROM VQT.Expr6 AS X - unexpected QUERY results

by Warren Gibson (JIRA)

DB2 9.1 & 9.7 - VQT query SELECT * FROM VQT.Expr6 AS X - unexpected QUERY results ---------------------------------------------------------------------------------- Key: TEIID-1193 URL: https://jira.jboss.org/browse/TEIID-1193 Project: Teiid Issue Type: Bug Affects Versions: 7.1 Environment: Teiid-7.1.0.CR2 Reporter: Warren Gibson Assignee: Steve Hawkins The following VQT query is producing CTC unexpected results in DB2 9.1 and 9.7. VDB is attached along with a DEBUG log file from CTC execution. SELECT * FROM VQT.Expr6 AS X When I submit the query plan source query straight to the source in Squirrel it also fails. Source query from plan: SELECT SMALLA.STRINGNUM, NULL FROM SMALLA Squirrel Error: DB2 SQL Error: SQLCODE=-206, SQLSTATE=42703, SQLERRMC=NULL, DRIVER=4.0.100 SQLState: 42703 ErrorCode: -206 Error: DB2 SQL Error: SQLCODE=-727, SQLSTATE=56098, SQLERRMC=2;-206;42703;NULL, DRIVER=4.0.100 SQLState: 56098 ErrorCode: -727 -- 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, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIID-1190) Procedure logic clean up

by Steve Hawkins (JIRA)

Procedure logic clean up ------------------------ Key: TEIID-1190 URL: https://jira.jboss.org/browse/TEIID-1190 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1 The procedure planning logic has several issues that should be addressed 1. RaiseErrorStatement extends AssignmentStatement, which is confusing the designer code. 2. Assigment/RaiseError/Declare have lots of specialized logic for dealing with commands. It would be much simplier to just use a scalar subquery to represent the command execution. This may need to be refined later if we want specialized handling for using the return value from storedprocedures and to use its cursor. 3. Validation is not run on dynamic sql commands. -- 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, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-1162) Document the recommended approach to using entitlements

by Van Halbert (JIRA)

Document the recommended approach to using entitlements ------------------------------------------------------- Key: TEIID-1162 URL: https://jira.jboss.org/browse/TEIID-1162 Project: Teiid Issue Type: Task Components: Documentation Reporter: Van Halbert Assignee: Steve Hawkins Priority: Blocker Document the recommended approach to using entitlements and indicate what happens when permissions are applied to a Virtual Layer for which the underlying (virtual) model already has entitlements assigned. Any concerns, regarding how data might be accidentally exposed, should be highlighted. Yes, we say an experienced person should be the one responsible for security, but we must also provide direction to this person in order that they be successful. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1028) Make Materialized Views first class objects in the system

by Van Halbert (JIRA)

Make Materialized Views first class objects in the system --------------------------------------------------------- Key: TEIID-1028 URL: https://jira.jboss.org/jira/browse/TEIID-1028 Project: Teiid Issue Type: Feature Request Reporter: Van Halbert Assignee: Steven Hawkins Fix For: 7.1 Rework the MetMatrix materialized views functionality to make mat views first class objects in the system. Full materialization control to an external source was being discussed as a designer based activity. -- 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

14 years, 4 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2010