November 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5106) Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid.

by sameer P (JIRA)

[ https://issues.jboss.org/browse/TEIID-5106?page=com.atlassian.jira.plugin... ] sameer P commented on TEIID-5106: --------------------------------- [~shawkins], there is a small thing in this. In the log messages, looks like the names of renamed table and the new name are swapped. Now it comes as "Table name <new_name> is not unique, renaming as <old_name>" :) > Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid. > -------------------------------------------------------------------------- > > Key: TEIID-5106 > URL: https://issues.jboss.org/browse/TEIID-5106 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Reporter: sameer P > Assignee: Steven Hawkins > Fix For: 10.0 > > > In Postgres/Oracle/MS , I can create two tables with the same name (but different cases): test12 and Test12 (by quoting it in create script) , but, Teiid complains saying duplicate table name and fails with the below error: > {code:java} > 16:53:11,161 WARN [org.teiid.RUNTIME] (Worker0_async-teiid-threads0) TEIID50036 VDB test.1 model "dsms" metadata failed to load. Reason:TEIID60013 Duplicate Table public.test12: org.teiid.metadata.DuplicateRecordException: TEIID60013 Duplicate Table public.test12 > at org.teiid.metadata.Schema.addTable(Schema.java:51) > at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:179) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:368) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:351) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:324) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:166) > at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:306) > at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:69) > at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) > at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) > at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) > at org.teiid.jboss.VDBService$6.run(VDBService.java:341) > at org.teiid.jboss.VDBService$7.run(VDBService.java:392) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5125) OData v4 doesn't work with Java 6

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5125?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-5125: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1506512|https://bugzilla.redhat.com/show_bug.cgi?id=1506512] from NEW to MODIFIED > OData v4 doesn't work with Java 6 > --------------------------------- > > Key: TEIID-5125 > URL: https://issues.jboss.org/browse/TEIID-5125 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.x-6.4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.12.x-6.4 > > > In the version reported, user can't access odata4 api: > {code} > 17:32:01,553 ERROR [org.teiid.ODATA] (http-0.0.0.0:8080-1) TEIID16050 Unable to process odata request due to: java.lang.Integer.compare(II)I with cause java.lang.Integer.compare(II)I: org.apache.olingo.server.api.ODataApplicationException: java.lang.Integer.compare(II)I > at org.teiid.olingo.service.TeiidServiceHandler.read(TeiidServiceHandler.java:173) [teiid-olingo-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.apache.olingo.server.core.requests.DataRequest$EntityRequest.execute(DataRequest.java:332) > at org.apache.olingo.server.core.requests.DataRequest.execute(DataRequest.java:255) > at org.apache.olingo.server.core.ServiceDispatcher.internalExecute(ServiceDispatcher.java:160) > at org.apache.olingo.server.core.ServiceDispatcher.execute(ServiceDispatcher.java:98) > at org.apache.olingo.server.core.OData4HttpHandler.process(OData4HttpHandler.java:67) > at org.teiid.olingo.web.ODataServlet.service(ODataServlet.java:43) [teiid-olingo-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.24.Final-redhat-1.jar:7.5.24.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.24.Final-redhat-1.jar:7.5.24.Final-redhat-1] > at org.teiid.olingo.web.ODataFilter.internalDoFilter(ODataFilter.java:231) [teiid-olingo-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.olingo.web.ODataFilter.doFilter(ODataFilter.java:100) [teiid-olingo-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.24.Final-redhat-1.jar:7.5.24.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.24.Final-redhat-1.jar:7.5.24.Final-redhat-1] > at org.teiid.olingo.web.CorsFilter.doFilter(CorsFilter.java:80) [teiid-olingo-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.24.Final-redhat-1.jar:7.5.24.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.24.Final-redhat-1.jar:7.5.24.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.24.Final-redhat-1.jar:7.5.24.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.24.Final-redhat-1.jar:7.5.24.Final-redhat-1] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.24.Final-redhat-1.jar:7.5.24.Final-redhat-1] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.17.Final-redhat-4.jar:7.5.17.Final-redhat-4] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:151) [jbossweb-7.5.24.Final-redhat-1.jar:7.5.24.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.24.Final-redhat-1.jar:7.5.24.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.24.Final-redhat-1.jar:7.5.24.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [jbossweb-7.5.24.Final-redhat-1.jar:7.5.24.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.5.24.Final-redhat-1.jar:7.5.24.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:656) [jbossweb-7.5.24.Final-redhat-1.jar:7.5.24.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.24.Final-redhat-1.jar:7.5.24.Final-redhat-1] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > Caused by: java.lang.NoSuchMethodError: java.lang.Integer.compare(II)I > at org.teiid.olingo.service.DocumentNode$1.compare(DocumentNode.java:389) [teiid-olingo-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.olingo.service.DocumentNode$1.compare(DocumentNode.java:386) [teiid-olingo-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at java.util.Arrays.mergeSort(Arrays.java:1270) [rt.jar:1.6.0_45] > at java.util.Arrays.sort(Arrays.java:1210) [rt.jar:1.6.0_45] > at java.util.Collections.sort(Collections.java:157) [rt.jar:1.6.0_45] > at org.teiid.olingo.service.DocumentNode.sortColumns(DocumentNode.java:386) [teiid-olingo-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.olingo.service.DocumentNode.buildQuery(DocumentNode.java:354) [teiid-olingo-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.olingo.service.ODataSQLBuilder.selectQuery(ODataSQLBuilder.java:184) [teiid-olingo-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.olingo.service.TeiidServiceHandler.read(TeiidServiceHandler.java:170) [teiid-olingo-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > ... 28 more > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5007) Changes to reduce Teiid in the cloud footprint

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5007?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5007: ---------------------------------- Fix Version/s: 10.1 (was: 10.x) > Changes to reduce Teiid in the cloud footprint > ---------------------------------------------- > > Key: TEIID-5007 > URL: https://issues.jboss.org/browse/TEIID-5007 > Project: Teiid > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.1 > > > A Teiid instance even as swarm or springboot needs additional considerations to minimize the runtime footprint. This includes: > * container aware auto-sizing. Detection of the number of cpus and available memory need refined - there are experimental settings being considered for containerized vms to better report these values and there is logic in WildFly and other projects that attempts better auto-detection. We also need to utilize the memory buffer space more and probably as off-heap space (and ideally direct operations on the serialized data) > * Subsystems required include JTA, webserver, security, which could be satisfied by slimmer alternative versions - especially if we make new assumptions, such as not utilizing xa transactions. > * Engine dependencies could be application specific - removing xml/xsl support, geometry support, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5131) Create ansible playbooks for the ansible service broker

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5131?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5131: ---------------------------------- Fix Version/s: 10.1 (was: 10.x) > Create ansible playbooks for the ansible service broker > ------------------------------------------------------- > > Key: TEIID-5131 > URL: https://issues.jboss.org/browse/TEIID-5131 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.1 > > > For some of the most common usage patterns, we should create playbooks that contribute service brokers via the ansible service broker. This could be: > salesforce as db > couchbase as db/odata > mongodb as db/odata > other openshift databases as odata -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5010) Swarm usage should be more configurable

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5010?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-5010: ------------------------------------- Assignee: Ramesh Reddy > Swarm usage should be more configurable > --------------------------------------- > > Key: TEIID-5010 > URL: https://issues.jboss.org/browse/TEIID-5010 > Project: Teiid > Issue Type: Sub-task > Components: WildFly Swarm > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 10.1 > > > When building a swarm uber jar the wildfly/swarm functionality remains the same regardless of what is needed. The wildfly fractions/subsystems need to be configurable so that we can drop systems, such as the web server, selectively. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5010) Swarm usage should be more configurable

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5010?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5010: ---------------------------------- Fix Version/s: 10.1 (was: 10.x) > Swarm usage should be more configurable > --------------------------------------- > > Key: TEIID-5010 > URL: https://issues.jboss.org/browse/TEIID-5010 > Project: Teiid > Issue Type: Sub-task > Components: WildFly Swarm > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 10.1 > > > When building a swarm uber jar the wildfly/swarm functionality remains the same regardless of what is needed. The wildfly fractions/subsystems need to be configurable so that we can drop systems, such as the web server, selectively. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4633) Odata $expand over Oracle tables generates bad query

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4633?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4633: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1506573|https://bugzilla.redhat.com/show_bug.cgi?id=1506573] from NEW to ON_QA > Odata $expand over Oracle tables generates bad query > ---------------------------------------------------- > > Key: TEIID-4633 > URL: https://issues.jboss.org/browse/TEIID-4633 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector, OData > Affects Versions: 9.1.1 > Reporter: Sergio Samayoa > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.2, 9.1.3, 8.12.x-6.4 > > > Query generated to obtain referenced records ($expand many to one) is generated with parentheses, > Generated query for Oracle*: > SELECT g_0."CATEGORY_ID", (g_0."CATEGORY_ID", g_0."NAME", g_0."LAST_UPDATE") FROM "SAKILA"."CATEGORY" g_0 > Generated query for MySQL is: > SELECT g_0.category_id, g_0.name, g_0.last_update FROM Sakila.category AS g_0 > * Note the parentheses enclosing all columns but PK, this raises "ORA-00907: missing right parenthesis". -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4147) matpg_datatype should include more type mappings

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4147?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4147: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1506558|https://bugzilla.redhat.com/show_bug.cgi?id=1506558] from NEW to ON_QA > matpg_datatype should include more type mappings > ------------------------------------------------ > > Key: TEIID-4147 > URL: https://issues.jboss.org/browse/TEIID-4147 > Project: Teiid > Issue Type: Bug > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.x-6.4 > > > matpg_datatype is missing mappings for varbinary and the single dimension array types in pg_type. We may need to consider using the original pg type names rather than the Teiid types names - at least for array handling and so clients there may be built-in expectations around basic types. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5132) max-active-plans property limit one higher than set.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5132?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-5132: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1508348 Bugzilla Update: Perform > max-active-plans property limit one higher than set. > ---------------------------------------------------- > > Key: TEIID-5132 > URL: https://issues.jboss.org/browse/TEIID-5132 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.x-6.4 > Reporter: Andrej Šmigala > Assignee: Steven Hawkins > Priority: Minor > > Setting the max-active-plans property limits the number of queries that are processed concurrently, however, in our testing, the actual number of concurrent queries is consistently one higher than the max-active-plans setting, i.e. setting max-active-plans to 1 allows two concurrent queries etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5132) max-active-plans property limit one higher than set.

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIID-5132: ------------------------------------- Summary: max-active-plans property limit one higher than set. Key: TEIID-5132 URL: https://issues.jboss.org/browse/TEIID-5132 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.12.x-6.4 Reporter: Andrej Šmigala Assignee: Steven Hawkins Priority: Minor Setting the max-active-plans property limits the number of queries that are processed concurrently, however, in our testing, the actual number of concurrent queries is consistently one higher than the max-active-plans setting, i.e. setting max-active-plans to 1 allows two concurrent queries etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2017