November 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5140) Teiid 10 postgres driver version

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5140?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5140: ---------------------------------- Fix Version/s: 10.1 10.0.1 > Teiid 10 postgres driver version > -------------------------------- > > Key: TEIID-5140 > URL: https://issues.jboss.org/browse/TEIID-5140 > Project: Teiid > Issue Type: Bug > Reporter: Lukáš Svačina > Assignee: Steven Hawkins > Fix For: 10.1, 10.0.1 > > > I tried several drivers from https://jdbc.postgresql.org/download.html and figured out that 9.4-1203 JDBC 42 is the newest working driver for my application. > > Newer drivers cause Teiid to fail on datasource creation with error "Reason:TEIID60011 No column found on table xxxx.pg_toast.pg_toast_16446 with name chunk_id" > Please update docs about what driver version is recommended (or tested) and if there is any reason to update to newer postgres drivers (what benefits it brings and how teiid uses it). > Might be good idea to ship driver within teiid package or at least keep updated _docs\teiid\datasources\postgresql\readme.txt_ to contain recommended driver name. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5140) Teiid 10 postgres driver version

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5140?page=com.atlassian.jira.plugin... ] Work on TEIID-5140 started by Steven Hawkins. --------------------------------------------- > Teiid 10 postgres driver version > -------------------------------- > > Key: TEIID-5140 > URL: https://issues.jboss.org/browse/TEIID-5140 > Project: Teiid > Issue Type: Bug > Reporter: Lukáš Svačina > Assignee: Steven Hawkins > Fix For: 10.1, 10.0.1 > > > I tried several drivers from https://jdbc.postgresql.org/download.html and figured out that 9.4-1203 JDBC 42 is the newest working driver for my application. > > Newer drivers cause Teiid to fail on datasource creation with error "Reason:TEIID60011 No column found on table xxxx.pg_toast.pg_toast_16446 with name chunk_id" > Please update docs about what driver version is recommended (or tested) and if there is any reason to update to newer postgres drivers (what benefits it brings and how teiid uses it). > Might be good idea to ship driver within teiid package or at least keep updated _docs\teiid\datasources\postgresql\readme.txt_ to contain recommended driver name. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5142) General OData error message has extra escaping

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5142: ------------------------------------- Summary: General OData error message has extra escaping Key: TEIID-5142 URL: https://issues.jboss.org/browse/TEIID-5142 Project: Teiid Issue Type: Quality Risk Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 10.1 Accessing odata4 with an invalid path gives: { "error": { "code": "TEIID16020", "message": "TEIID16020 Invalid URL, no vdb name found on the path. It should be in the form of \"http:\/\/<host>[:<port>]\/odata4\/vdbname\/modelname\/...\"" } } With extra escaping in the url description. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5141) Osisoft translator - ANY and SOME expressions cause syntax errors on datasource

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5141?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-5141: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Osisoft translator - ANY and SOME expressions cause syntax errors on datasource > ------------------------------------------------------------------------------- > > Key: TEIID-5141 > URL: https://issues.jboss.org/browse/TEIID-5141 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.x-6.4 > Reporter: Andrej Šmigala > Assignee: Ramesh Reddy > > Running a query such as > {code:sql} > SELECT INTKEY, STRINGKEY, FLOATNUM FROM BQT1.SMALLA WHERE FLOATNUM <> SOME (SELECT FLOATNUM FROM BQT1.SMALLA WHERE STRINGKEY = 10) > {code} > gets translated as > {code:sql} > SELECT g_0.IntKey, g_0.StringKey, g_0.FloatNum FROM dvqe..SmallA AS g_0 WHERE g_0.FloatNum <> SOME (SELECT g_1.FloatNum FROM dvqe..SmallA AS g_1 WHERE g_1.StringKey = '10') > {code} > and fails with > {noformat} > com.osisoft.rdsa.RdsaException: [PIOLEDBENT] [SQL Parser] [Line 1:100] Missing ) at 'SELECT' > [Line 1:171] Extraneous ')' > {noformat} > Same thing when the SOME keyword is replaced with ANY (as in, ANY is translated to the exact same query, with 'SOME', which is understandable, since they _should_ be equivalent). > This appears to be a bug in Osisoft PI, since issuing the same query with ANY against the datasource (without teiid involvement) works, so I suggest translating SOME as ANY as a workaround. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5141) Osisoft translator - ANY and SOME expressions cause syntax errors on datasource

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIID-5141: ------------------------------------- Summary: Osisoft translator - ANY and SOME expressions cause syntax errors on datasource Key: TEIID-5141 URL: https://issues.jboss.org/browse/TEIID-5141 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 8.12.x-6.4 Reporter: Andrej Šmigala Assignee: Steven Hawkins Running a query such as {code:sql} SELECT INTKEY, STRINGKEY, FLOATNUM FROM BQT1.SMALLA WHERE FLOATNUM <> SOME (SELECT FLOATNUM FROM BQT1.SMALLA WHERE STRINGKEY = 10) {code} gets translated as {code:sql} SELECT g_0.IntKey, g_0.StringKey, g_0.FloatNum FROM dvqe..SmallA AS g_0 WHERE g_0.FloatNum <> SOME (SELECT g_1.FloatNum FROM dvqe..SmallA AS g_1 WHERE g_1.StringKey = '10') {code} and fails with {noformat} com.osisoft.rdsa.RdsaException: [PIOLEDBENT] [SQL Parser] [Line 1:100] Missing ) at 'SELECT' [Line 1:171] Extraneous ')' {noformat} Same thing when the SOME keyword is replaced with ANY (as in, ANY is translated to the exact same query, with 'SOME', which is understandable, since they _should_ be equivalent). This appears to be a bug in Osisoft PI, since issuing the same query with ANY against the datasource (without teiid involvement) works, so I suggest translating SOME as ANY as a workaround. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 commented on TEIID-5132: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1508348|https://bugzilla.redhat.com/show_bug.cgi?id=1508348] from NEW to MODIFIED > 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 > Fix For: 8.12.x-6.4, 10.1 > > > 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)

8 years, 4 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 commented on TEIID-5131: --------------------------------------- It's under https://github.com/shawkins/teiid-openshift-templates for now. It relies on shell scripts, which could also be converted / expanded into a makefile. > 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)

8 years, 4 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 commented on TEIID-5131: --------------------------------------- Demo'd the initial scripts for a simple salesforce service. I'm using a configmap to inject both a new configuration and the vdb via the template, but needed to introduce extra handling for the deployments. Next steps may include: - Could update the docker entry point with add datasource cli call to simply injecting the whole configuration - clustering - probably need to start with standalone-ha and utilize and jgroups specifics from the infinispan cluster.xml - slimmer eap config, remove the unnecessary subsystems - add a readiness health check, which could be an admin call testing for vdb deployment The next demo will be for mongodb. I'll put the current work in my repo for now as we may not yet need to replace the basic docker image created by the community or in the jboss dockerhub. > 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)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5139) Reached maximum thread count "10" for worker pool "async-teiid-threads"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5139?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5139: --------------------------------------- The first thing that needs addressed is that the warning message is incorrect. In the TEIID-3519 change we didn't differentiate between the dqp worker pool and the async pool. > Already tried what is explained here but applied for the standalone mode without any success. I see there was a dangling question that wasn't answered there, so there may be something amiss. It looks like you are running in standalone mode though. What did you attempt to change those attributes to? Did you use the cli or a direct edit to the standalone.xml? Unfortunately none of the thread dumps show anywhere close to 10 active async workers, so it's hard to say why things are waiting in the queue. > Reached maximum thread count "10" for worker pool "async-teiid-threads" > ----------------------------------------------------------------------- > > Key: TEIID-5139 > URL: https://issues.jboss.org/browse/TEIID-5139 > Project: Teiid > Issue Type: Bug > Affects Versions: 10.0 > Environment: Teiid 10.0.0 > Wildfly 11 > RHEL 7.2 > Reporter: Pedro Inácio > Assignee: Steven Hawkins > Attachments: teiid.7z > > > Cannot configure system to remove the following warning: > *TEIID30009 Reached maximum thread count "10" for worker pool "async-teiid-threads" with a queue size high of "44". Queued work waited 500 ms prior to executing. To avoid queuing of work you may consider increasing "max-threads" or decreasing the "max-active-plans" in the "standalone-teiid.xml" file.* > Already tried what is explained [here|https://developer.jboss.org/thread/275761] but applied for the standalone mode without any success. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5136) Osisoft translator - NPE when running query with LATERAL JOIN

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5136?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-5136: ----------------------------------- Assignee: Ramesh Reddy > Osisoft translator - NPE when running query with LATERAL JOIN > ------------------------------------------------------------- > > Key: TEIID-5136 > URL: https://issues.jboss.org/browse/TEIID-5136 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Reporter: Andrej Šmigala > Assignee: Ramesh Reddy > Fix For: 10.1 > > > Running the following query: > {code:sql} > SELECT bqt2.smalla.intkey, g2.intkey, bqt2.smalla.bytenum FROM bqt2.smalla LEFT JOIN LATERAL (SELECT intkey FROM bqt2.mediuma WHERE bqt2.smalla.bytenum = bqt2.mediuma.bytenum) AS g2 ON true > {code} > results in a NPE in teiid (before sending source src command). > Stacktrace: > {noformat} > Connector worker process failed for atomic-request=vEbs99yd+srV.1.0.1: java.lang.NullPointerException > at org.teiid.translator.jdbc.pi.PIExecutionFactory.translate(PIExecutionFactory.java:273) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4] > at org.teiid.translator.jdbc.SQLConversionVisitor.append(SQLConversionVisitor.java:111) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4] > at org.teiid.language.visitor.SQLStringVisitor.append(SQLStringVisitor.java:106) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.language.visitor.SQLStringVisitor.visit(SQLStringVisitor.java:767) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.language.Select.acceptVisitor(Select.java:110) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.language.visitor.SQLStringVisitor.append(SQLStringVisitor.java:91) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.translator.jdbc.SQLConversionVisitor.append(SQLConversionVisitor.java:130) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4] > at org.teiid.translator.jdbc.TranslatedCommand.translateCommand(TranslatedCommand.java:76) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4] > at org.teiid.translator.jdbc.JDBCBaseExecution.translateCommand(JDBCBaseExecution.java:120) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:114) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:363) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_141] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_141] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_141] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_141] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy79.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_141] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) > 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:1149) [rt.jar:1.8.0_141] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_141] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141] > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 November 2017