February 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2797) buffer full requests is not cleaned up properly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2797?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2797: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1051562|https://bugzilla.redhat.com/show_bug.cgi?id=1051562] from ASSIGNED to MODIFIED > buffer full requests is not cleaned up properly > ----------------------------------------------- > > Key: TEIID-2797 > URL: https://issues.jboss.org/browse/TEIID-2797 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 7.7.9, 8.4.2, 8.7 > > Attachments: TEIID-2797.patch > > > buffer full plans are held as the full work item, but we are cleaning them up by the request id. This means that the full plans will accumulate over time. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2770) Imported vdbs have their roles added to the actual instance of the importing vdb

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2770?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2770: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1062245|https://bugzilla.redhat.com/show_bug.cgi?id=1062245] from NEW to MODIFIED > Imported vdbs have their roles added to the actual instance of the importing vdb > -------------------------------------------------------------------------------- > > Key: TEIID-2770 > URL: https://issues.jboss.org/browse/TEIID-2770 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6, 8.4.2 > > > Imported roles should be stored on a new instance of the role map on the merged vdb instance, not on the original vdb. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2794) ambiguous function calls are not properly handled

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2794?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2794: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1050001|https://bugzilla.redhat.com/show_bug.cgi?id=1050001] from ASSIGNED to MODIFIED > ambiguous function calls are not properly handled > ------------------------------------------------- > > Key: TEIID-2794 > URL: https://issues.jboss.org/browse/TEIID-2794 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.2, 8.7 > > > For user defined or possibly translator functions that are given the same name the first exact match to the function name and types will be used as the function rather than reporting an ambiguous match. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2766) OData large batch size does not allow all results to be returned to the client in a single batch

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2766?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2766: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1041561|https://bugzilla.redhat.com/show_bug.cgi?id=1041561] from ASSIGNED to MODIFIED > OData large batch size does not allow all results to be returned to the client in a single batch > ------------------------------------------------------------------------------------------------ > > Key: TEIID-2766 > URL: https://issues.jboss.org/browse/TEIID-2766 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.4 > Environment: OData client connecting to Teiid > Reporter: Marc Shirley > Assignee: Steven Hawkins > Labels: final > Fix For: 8.6, 8.4.2 > > > OData large batch-size, for example -1 to get all results in 1 response, doesn't work. Largest tested value that does work 51210. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2656) Teiid OData Servlet throws java.lang.NullPointerException on every GET

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2656?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2656: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1060217|https://bugzilla.redhat.com/show_bug.cgi?id=1060217] from NEW to MODIFIED > Teiid OData Servlet throws java.lang.NullPointerException on every GET > ---------------------------------------------------------------------- > > Key: TEIID-2656 > URL: https://issues.jboss.org/browse/TEIID-2656 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.3, 8.4 > Environment: Windows 7 64 bit > Oracle JDK 1.7.0 update 17 > JBoss AS 7.1.1 + Teiid 8.3 (both resteasy-jaxrs 2.3.5 and 2.3.7) > JBoss EAP 6.1 + Teiid 8.4 (resteasy-jaxrs 2.3.6) > Reporter: John Muller > Assignee: Ramesh Reddy > Labels: final > Fix For: 8.5, 8.4.2 > > Attachments: server.log, Teiid_8.4_on_JBoss_EAP_6.1Alpha_RHEL6.log > > > A simple GET on any Teiid 8.3 or 8.4 OData ReST resource results in a Null Pointer: > 11:43:20,166 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/odata].[Resteasy]] (http-localhost-127.0.0.1-8080-2) Servlet.service() for servlet Resteasy threw exception: java.lang.NullPointerException > at com.ctc.wstx.sw.BaseStreamWriter.writeCharacters(BaseStreamWriter.java:447) > at org.codehaus.stax2.ri.Stax2EventWriterImpl.add(Stax2EventWriterImpl.java:124) > at org.odata4j.stax2.staximpl.StaxXMLWriter2.writeText(StaxXMLWriter2.java:108) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] > at org.odata4j.format.xml.AtomErrorFormatWriter.writeError(AtomErrorFormatWriter.java:31) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] > at org.odata4j.format.xml.AtomErrorFormatWriter.write(AtomErrorFormatWriter.java:20) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] > at org.odata4j.format.xml.AtomErrorFormatWriter.write(AtomErrorFormatWriter.java:15) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] > at org.teiid.odata.ODataExceptionMappingProvider.toResponse(ODataExceptionMappingProvider.java:55) [classes:] > at org.teiid.odata.ODataExceptionMappingProvider.toResponse(ODataExceptionMappingProvider.java:42) [classes:] > at org.jboss.resteasy.core.SynchronousDispatcher.executeExceptionMapper(SynchronousDispatcher.java:344) [resteasy-jaxrs-2.3.7.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.unwrapException(SynchronousDispatcher.java:373) [resteasy-jaxrs-2.3.7.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:362) [resteasy-jaxrs-2.3.7.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:233) [resteasy-jaxrs-2.3.7.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:209) [resteasy-jaxrs-2.3.7.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:557) [resteasy-jaxrs-2.3.7.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.7.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.7.Final.jar:] > at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:97) [classes:] > at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.7.Final.jar:] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:489) [jbossweb-7.0.13.Final.jar:] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] > at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_17] -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2766) OData large batch size does not allow all results to be returned to the client in a single batch

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2766?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2766: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1041561|https://bugzilla.redhat.com/show_bug.cgi?id=1041561] from MODIFIED to ASSIGNED > OData large batch size does not allow all results to be returned to the client in a single batch > ------------------------------------------------------------------------------------------------ > > Key: TEIID-2766 > URL: https://issues.jboss.org/browse/TEIID-2766 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.4 > Environment: OData client connecting to Teiid > Reporter: Marc Shirley > Assignee: Steven Hawkins > Labels: final > Fix For: 8.6, 8.4.2 > > > OData large batch-size, for example -1 to get all results in 1 response, doesn't work. Largest tested value that does work 51210. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2842) Impala/ HIVE2: Unsupported compress file

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2842?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2842: ------------------------------------- It did not work with renaming, or with out .gz extension. I asked the question on the same JIRA https://issues.cloudera.org/browse/IMPALA-14 Is .gz files something your process generates, that you want to add support for through Teiid/Impala? If that is chosen by your system's user then may be not having this capability is OK, as they could not used Impala in either case? > Impala/ HIVE2: Unsupported compress file > ----------------------------------------- > > Key: TEIID-2842 > URL: https://issues.jboss.org/browse/TEIID-2842 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.6 > Environment: Impala/HIVE2 with Teiid > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Labels: teiid > Fix For: 8.7 > > > Teiid makes a query call "Describe table" in HiveMetadataProcessor.addTable(....). However, if the table contains compress file, HIVE2 driver would return the following execption: > {code} > java.sql.SQLException: AnalysisException: Failed to load metadata for table: default.omniturelogs > CAUSED BY: TableLoadingException: Failed to load metadata for table: > omniturelogs > CAUSED BY: RuntimeException: Compressed text files are not supported: hdfs://localhost.localdomain:8020/user/cloudera/omniturelogs/Omniture.0.tsv.gz > at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:161) > at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:149) > at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:182) > at org.apache.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:246) > at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208) > at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208) > at org.teiid.translator.hive.HiveMetadataProcessor.addTable(HiveMetadataProcessor.java:112) > at org.teiid.translator.hive.HiveMetadataProcessor.getConnectorMetadata(HiveMetadataProcessor.java:48) > > at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:311) > ... 155 more > {code} > Maybe Teiid should call "DESCRIBE FORMATTED table" for table that contains compress file. > Reference: > http://grokbase.com/t/cloudera/impala-user/13b7c9apmx/impala-failed-to-qu... -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2766) OData large batch size does not allow all results to be returned to the client in a single batch

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2766?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2766: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1041561|https://bugzilla.redhat.com/show_bug.cgi?id=1041561] from ASSIGNED to MODIFIED > OData large batch size does not allow all results to be returned to the client in a single batch > ------------------------------------------------------------------------------------------------ > > Key: TEIID-2766 > URL: https://issues.jboss.org/browse/TEIID-2766 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.4 > Environment: OData client connecting to Teiid > Reporter: Marc Shirley > Assignee: Steven Hawkins > Labels: final > Fix For: 8.6, 8.4.2 > > > OData large batch-size, for example -1 to get all results in 1 response, doesn't work. Largest tested value that does work 51210. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2846) Add procedure parameter native type extension property handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2846?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2846. ----------------------------------- Resolution: Done Added an override check for the native type extension in procedureparameter. > Add procedure parameter native type extension property handling > --------------------------------------------------------------- > > Key: TEIID-2846 > URL: https://issues.jboss.org/browse/TEIID-2846 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7 > > > TEIID-2644 adds out parameter cursor handling for oracle, and adds a native type property to procedure parameters (just like regular columns). TEIIDDES-1863 adds support as an extension property, which needs handling on the teiid side. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2729) Dynamic VDB xml requires sibling elements to be in a certain order

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2729?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2729. ----------------------------------- Resolution: Deferred The only other approach I can see is to just allow any xml. However that doesn't seem a good solution either. Marking as deferred for now. > Dynamic VDB xml requires sibling elements to be in a certain order > ------------------------------------------------------------------ > > Key: TEIID-2729 > URL: https://issues.jboss.org/browse/TEIID-2729 > Project: Teiid > Issue Type: Enhancement > Components: AdminApi > Affects Versions: 8.5 > Reporter: Mark Drilling > Assignee: Steven Hawkins > Fix For: 8.7 > > > In my *-vdb.xml, I have a model defined per following snippet: > <model name="myModel" type="PHYSICAL" visible="true"> > <source name="myModel" translator-name="hive" connection-jndi-name="Hive12Src" /> > <property name="trimColumnNames" value="true" /> > </model> > The vdb.xml failed to parse, so I moved the <property> element ahead of <source> and then it worked. > I don't think element ordering should matter in this case? -- 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, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2014