February 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2133) Handle enterprise/UD types in metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2133?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2133. ----------------------------------- Fix Version/s: 8.1 Resolution: Done Checked in under TEIID-2083 > Handle enterprise/UD types in metadata > -------------------------------------- > > Key: TEIID-2133 > URL: https://issues.jboss.org/browse/TEIID-2133 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Affects Versions: 8.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.1 > > > The ddl parsing/export logic handles runtime and built-in types, but enterprise types (from designer vdbs, typically used with xml document models) are not supported. > We may have to wait on implementing this until we make the type system more extensible in general. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2392) Pushdown common table query invalid

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2392?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2392: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=916248 > Pushdown common table query invalid > ----------------------------------- > > Key: TEIID-2392 > URL: https://issues.jboss.org/browse/TEIID-2392 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > If a common table expression that can produce a query that contains different column names than either the assumed or explicit names in the with clause, then the pushed query can contain invalid column references. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2410) issues with output buffer blocking

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2410?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2410: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=916247 > issues with output buffer blocking > ---------------------------------- > > Key: TEIID-2410 > URL: https://issues.jboss.org/browse/TEIID-2410 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > when a local connection (regardless of using the calling thread) blocks on the output buffer (which cannot happen with forward only and using the calling thread, but due to another issue can occur with a scroll insensitive result) no corresponding process thread is awakened to process pending work. > Output blocking should also be disabled for non-forward only results. This was disabled at some point by a refactoring to reuse the output buffer from the plan. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2386) Add Preview VDB Filter back to RHQ Plugin

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIID-2386?page=com.atlassian.jira.plugin... ] Ted Jones updated TEIID-2386: ----------------------------- Git Pull Request: https://github.com/teiid/teiid-rhq/pull/1 > Add Preview VDB Filter back to RHQ Plugin > ----------------------------------------- > > Key: TEIID-2386 > URL: https://issues.jboss.org/browse/TEIID-2386 > Project: Teiid > Issue Type: Feature Request > Components: RHQ > Affects Versions: 8.3 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.3 > > > In the pre-8.x version of the Teiid RHQ plugin, we had a filter for preview VDBs. We need to add that to the 8.x Teiid RHQ plugin as well. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2412) OData does not handle exceptions correctly

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2412?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2412. --------------------------------- Labels: CR1 (was: ) Resolution: Done Added overloaded the ExceptionMapper that handles the Web engine thrown errors much more gracefully such that all exceptions handled rather than swallowed. > OData does not handle exceptions correctly > ------------------------------------------ > > Key: TEIID-2412 > URL: https://issues.jboss.org/browse/TEIID-2412 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.3 > > > When a unexpected exception occurs, OData implementation masks correct error occurred and throws following > {code} > org.jboss.resteasy.core.ContextParameterInjector$GenericDelegatingProxy.invoke(ContextParameterInjector.java:53) > $Proxy33.getBaseUri(Unknown Source) > org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:54) org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:37) org.odata4j.producer.resources.ExceptionMappingProvider.getODataProducer(ExceptionMappingProvider.java:85) org.odata4j.producer.resources.ExceptionMappingProvider.toResponse(ExceptionMappingProvider.java:53) > org.odata4j.producer.resources.ExceptionMappingProvider.toResponse(ExceptionMappingProvider.java:35) org.jboss.resteasy.core.SynchronousDispatcher.executeExceptionMapper(SynchronousDispatcher.java:324) > org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:229) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:123) > org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:97) > org.teiid.odata.ODataServlet.service(ODataServlet.java:61) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) > javax.servlet.http.HttpServlet.service(HttpServlet.java:847) > {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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2412) OData does not handle exceptions correctly

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2412?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2412: -------------------------------- Affects Version/s: 8.3 > OData does not handle exceptions correctly > ------------------------------------------ > > Key: TEIID-2412 > URL: https://issues.jboss.org/browse/TEIID-2412 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.3 > > > When a unexpected exception occurs, OData implementation masks correct error occurred and throws following > {code} > org.jboss.resteasy.core.ContextParameterInjector$GenericDelegatingProxy.invoke(ContextParameterInjector.java:53) > $Proxy33.getBaseUri(Unknown Source) > org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:54) org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:37) org.odata4j.producer.resources.ExceptionMappingProvider.getODataProducer(ExceptionMappingProvider.java:85) org.odata4j.producer.resources.ExceptionMappingProvider.toResponse(ExceptionMappingProvider.java:53) > org.odata4j.producer.resources.ExceptionMappingProvider.toResponse(ExceptionMappingProvider.java:35) org.jboss.resteasy.core.SynchronousDispatcher.executeExceptionMapper(SynchronousDispatcher.java:324) > org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:229) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:123) > org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:97) > org.teiid.odata.ODataServlet.service(ODataServlet.java:61) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) > javax.servlet.http.HttpServlet.service(HttpServlet.java:847) > {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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2386) Add Preview VDB Filter back to RHQ Plugin

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIID-2386?page=com.atlassian.jira.plugin... ] Ted Jones updated TEIID-2386: ----------------------------- https://github.com/teiid/teiid-rhq/pull/1 > Add Preview VDB Filter back to RHQ Plugin > ----------------------------------------- > > Key: TEIID-2386 > URL: https://issues.jboss.org/browse/TEIID-2386 > Project: Teiid > Issue Type: Feature Request > Components: RHQ > Affects Versions: 8.3 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.3 > > > In the pre-8.x version of the Teiid RHQ plugin, we had a filter for preview VDBs. We need to add that to the 8.x Teiid RHQ plugin as well. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2386) Add Preview VDB Filter back to RHQ Plugin

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIID-2386?page=com.atlassian.jira.plugin... ] Ted Jones resolved TEIID-2386. ------------------------------ Resolution: Done > Add Preview VDB Filter back to RHQ Plugin > ----------------------------------------- > > Key: TEIID-2386 > URL: https://issues.jboss.org/browse/TEIID-2386 > Project: Teiid > Issue Type: Feature Request > Components: RHQ > Affects Versions: 8.3 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.3 > > > In the pre-8.x version of the Teiid RHQ plugin, we had a filter for preview VDBs. We need to add that to the 8.x Teiid RHQ plugin as well. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2412) OData does not handle exceptions correctly

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2412: ----------------------------------- Summary: OData does not handle exceptions correctly Key: TEIID-2412 URL: https://issues.jboss.org/browse/TEIID-2412 Project: Teiid Issue Type: Bug Components: Server Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.3 When a unexpected exception occurs, OData implementation masks correct error occurred and throws following {code} org.jboss.resteasy.core.ContextParameterInjector$GenericDelegatingProxy.invoke(ContextParameterInjector.java:53) $Proxy33.getBaseUri(Unknown Source) org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:54) org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:37) org.odata4j.producer.resources.ExceptionMappingProvider.getODataProducer(ExceptionMappingProvider.java:85) org.odata4j.producer.resources.ExceptionMappingProvider.toResponse(ExceptionMappingProvider.java:53) org.odata4j.producer.resources.ExceptionMappingProvider.toResponse(ExceptionMappingProvider.java:35) org.jboss.resteasy.core.SynchronousDispatcher.executeExceptionMapper(SynchronousDispatcher.java:324) org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:229) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:123) org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:97) org.teiid.odata.ODataServlet.service(ODataServlet.java:61) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) {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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2249) Enable the use of temporary tables for those data sources that support them instead of IN criteria for EDS

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2249?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2249: ---------------------------------- Fix Version/s: 8.4 (was: 8.3) pushing to 8.4 > Enable the use of temporary tables for those data sources that support them instead of IN criteria for EDS > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-2249 > URL: https://issues.jboss.org/browse/TEIID-2249 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.4 > > > Our proposal is to allow for the more efficient use of large ad-hoc result-sets by rather than creating a long 'IN' list, inserting them in to a temporary table - for example a # table in Sybase and SQL Server - and then generating an SQL join to that instead. > One of the difference to materialized views (or at least my understanding), is that this work happens at a data-source rather than within the Teiid server. -- 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

11 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2013