January 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2334) Add keys to system tables

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2334?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2334. --------------------------------- Resolution: Done All the SYS model tables contain PK and FK definitions. This is committed as part of TEIID-1854 > Add keys to system tables > ------------------------- > > Key: TEIID-2334 > URL: https://issues.jboss.org/browse/TEIID-2334 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.3 > > > The metadata changes to implement indexing on the system tables means that it is quite appropriate to include primary keys / indexes on system tables. We should also probably add unique constraints to uids. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2314) Unable to read class Name of resource adapter

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2314?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2314. --------------------------------- Resolution: Done Added code to return the resource-adaptor and managed-connection-factory class names in the template definitions for the RAR files. These are added as read-only advanced properties that can not be modified by the user. The new properties added are * resourceadapter-class * managedconnectionfactory-class > Unable to read class Name of resource adapter > --------------------------------------------- > > Key: TEIID-2314 > URL: https://issues.jboss.org/browse/TEIID-2314 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.1 > Reporter: Kamran Muhammad > Assignee: Ramesh Reddy > Fix For: 8.3 > > > We can read the coinfig properties of any resource adapter (*.rar). However we can not read the ManagedConnectionFactory class name and some other information in resource adapter rars. > Following link explains how to read properties, however mentions that need some modification in teiid subsystem to show class name also. > https://community.jboss.org/message/778401 -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2344) Determine database version automatically

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2344?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2344: ---------------------------------- Fix Version/s: (was: 8.3) I'll have to give this one some more thought as it would change the existing logic that does not require a connection to determine capabilities. Perhaps we could reset the cached capabilities once a connection becomes available - the issue would be that any cached plans would be built against the old capabilities and would need invalidated. > Determine database version automatically > ---------------------------------------- > > Key: TEIID-2344 > URL: https://issues.jboss.org/browse/TEIID-2344 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > It would be helpful if we could determine the database version automatically from the database metadata rather than relying on the user setting. Of course if the property setting is present we shouldn't override it. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2344) Determine database version automatically

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2344: ------------------------------------- Summary: Determine database version automatically Key: TEIID-2344 URL: https://issues.jboss.org/browse/TEIID-2344 Project: Teiid Issue Type: Enhancement Components: JDBC Connector Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.3 It would be helpful if we could determine the database version automatically from the database metadata rather than relying on the user setting. Of course if the property setting is present we shouldn't override it. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1854) OData server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-1854?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-1854: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=892717 > OData server > ------------ > > Key: TEIID-1854 > URL: https://issues.jboss.org/browse/TEIID-1854 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Mark Addleman > Assignee: Ramesh Reddy > Fix For: 8.3 > > > Teiid should act as an OData server as well as a JDBC server. This is not TEIID-1757 as that is about Teiid being an OData client. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2343) is_autoincrement not set for SQL Server identity columns

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2343?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2343. ----------------------------------- Resolution: Done Added a general method to the metadata importer to modify the columns as they are added and to check for the identity property type name suffix in the sql server importer. > is_autoincrement not set for SQL Server identity columns > -------------------------------------------------------- > > Key: TEIID-2343 > URL: https://issues.jboss.org/browse/TEIID-2343 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > The MS JDBC 4 driver still does not correctly report the is_autoincrement column in the JDBC metadata, thus dynamic vdbs will not have that value set. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2343) is_autoincrement not set for SQL Server identity columns

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2343: ------------------------------------- Summary: is_autoincrement not set for SQL Server identity columns Key: TEIID-2343 URL: https://issues.jboss.org/browse/TEIID-2343 Project: Teiid Issue Type: Quality Risk Components: JDBC Connector Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.3 The MS JDBC 4 driver still does not correctly report the is_autoincrement column in the JDBC metadata, thus dynamic vdbs will not have that value set. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2331) TEIID30019 Unexpected exception for request kfhsdoaNXYfM.1: java.lang.NullPointerException

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2331?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2331. ----------------------------------- Resolution: Cannot Reproduce Bug Marking as cannot reproduce. Please reopen if reproduced against a known version. > TEIID30019 Unexpected exception for request kfhsdoaNXYfM.1: java.lang.NullPointerException > ------------------------------------------------------------------------------------------ > > Key: TEIID-2331 > URL: https://issues.jboss.org/browse/TEIID-2331 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.1 > Environment: Windows 7 > Reporter: Sabina Norderhaug > Assignee: Steven Hawkins > Priority: Minor > > We are getting this exception during continious execution. Looks like client cancelling the execution > 16:13:16,171 ERROR [org.teiid.PROCESSOR] (Worker6_QueryProcessorQueue902) TEIID30019 Unexpected exception for request kfhsdoaNXYfM.1: java.lang.NullPointerException > at org.teiid.dqp.internal.process.RequestWorkItem.sendResultsIfNeeded(RequestWorkItem.java:753) > at org.teiid.dqp.internal.process.RequestWorkItem$1.flushBatchDirect(RequestWorkItem.java:557) > at org.teiid.query.processor.BatchCollector.flushBatch(BatchCollector.java:191) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:166) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:382) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:291) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:219) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:249) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_03] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_03] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03] -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2341) Better handling for outer join restriction pushdown

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2341?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2341. ----------------------------------- Resolution: Done Added compensation to push inner joins as outer joins (or to detect when the join can be represented via an outer join). Also added the PRESERVE hint to from clause items. > Better handling for outer join restriction pushdown > --------------------------------------------------- > > Key: TEIID-2341 > URL: https://issues.jboss.org/browse/TEIID-2341 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > For some sources (such as salesforce) they are restricted to outer joins. Queries entered as inner joins or are effectively the same using an outer join should still be pushed to the source. > It would also be good to have a hint to simply preserve the join structure as entered by the user to give them more control over the processing. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2342) NullPointerException in TempMetadataID

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2342?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2342: ---------------------------------- Fix Version/s: 8.3 Affects Version/s: 7.4 (was: 8.1) Moving the affected version back to 7.4. Global/session tempmetadataids can be accessed by multiple threads to have the quick cache accessed and thus may have issues if unsynchronized. > NullPointerException in TempMetadataID > -------------------------------------- > > Key: TEIID-2342 > URL: https://issues.jboss.org/browse/TEIID-2342 > Project: Teiid > Issue Type: Bug > Affects Versions: 7.4 > Reporter: RAKESH BALGURI > Assignee: Steven Hawkins > Fix For: 8.3 > > > NullPointerException in TempMetadataID > java.lang.NullPointerException > at java.util.LinkedHashMap.get(LinkedHashMap.java:337) > at org.teiid.query.metadata.TempMetadataID.getProperty(TempMetadataID.java:304) > at org.teiid.query.metadata.TempMetadataAdapter.getFromMetadataCache(TempMetadataAdapter.java:690) > at org.teiid.query.resolver.util.ResolverUtil.getGroupInfo(ResolverUtil.java:468) > at org.teiid.query.resolver.util.ResolverUtil.resolveElementsInGroup(ResolverUtil.java:461) > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.getOutputCols(NewCalculateCostUtil.java:567) > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.createColStats(NewCalculateCostUtil.java:515) > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.estimateSourceNodeCost(NewCalculateCostUtil.java:503) > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.computeNodeCost(NewCalculateCostUtil.java:153) > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.updateCardinality(NewCalculateCostUtil.java:135) > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.updateCardinality(NewCalculateCostUtil.java:132) > at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.computeCostForTree(NewCalculateCostUtil.java:121) > at org.teiid.query.optimizer.relational.rules.JoinRegion.initializeCostingInformation(JoinRegion.java:399) > at org.teiid.query.optimizer.relational.rules.RulePlanJoins.execute(RulePlanJoins.java:161) > at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:457) > at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:199) > at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:188) > at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:434) > at org.teiid.dqp.internal.process.PreparedStatementRequest.generatePlan(PreparedStatementRequest.java:157) > at org.teiid.dqp.internal.process.Request.processRequest(Request.java:454) > at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:532) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:280) -- 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

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2013