November 2017 - teiid-issues - Jboss List Archives

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

by Lukáš Svačina (JIRA)

Lukáš Svačina created TEIID-5140: ------------------------------------ Summary: 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 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)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5133) XmlTable path language is not always identical to XPathValue expressions

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5133?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-5133: ------------------------------- Fix Version/s: 8.12.x-6.4 > XmlTable path language is not always identical to XPathValue expressions > ------------------------------------------------------------------------ > > Key: TEIID-5133 > URL: https://issues.jboss.org/browse/TEIID-5133 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.3.4 > Environment: teiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Fix For: 10.0, 8.12.x-6.4, 9.2.7, 9.3.5 > > > The same Path value, used in XPathValue and XmlTable->Path brings different results. > That is for the following query: > {code:sql} > Select * From > (select '<root> > <item> > <id>id1</id> > <val>val1</val> > </item> > </root>' as resp) w, > XMLTABLE( > '/root' passing XMLPARSE(document w.resp) columns > valOption2 string PATH 'item[id = "id1"]/val' > --,valOption1 string PATH 'item[id/text() = "id1"]/val' > ) x;; > {code} > returned value for "valOption2" will be changed from "val1" to "null" that is incorrect and unexpected behavior. > Using "node/text()" in Path expressions may result in side effects. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5136?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-5136: ------------------------------------- Fix Version/s: 10.1 Assignee: (was: Steven Hawkins) > 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 > 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)

7 years, 2 months

1
0
0 / 0

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

by Pedro Inácio (JIRA)

[ https://issues.jboss.org/browse/TEIID-5139?page=com.atlassian.jira.plugin... ] Pedro Inácio commented on TEIID-5139: ------------------------------------- 1) The problem occurs when Teiid is starting. Dump attached. 2) Around 20 VDBs. 3) How can I see that? (how may sources need to have metadata r [^teiid.7z] etrieved) > 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)

7 years, 2 months

1
0
0 / 0

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

by Pedro Inácio (JIRA)

[ https://issues.jboss.org/browse/TEIID-5139?page=com.atlassian.jira.plugin... ] Pedro Inácio updated TEIID-5139: -------------------------------- Attachment: teiid.7z > 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)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4835) Implement column level incoming dependencies

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4835?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4835: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1500505|https://bugzilla.redhat.com/show_bug.cgi?id=1500505] from ASSIGNED to MODIFIED > Implement column level incoming dependencies > -------------------------------------------- > > Key: TEIID-4835 > URL: https://issues.jboss.org/browse/TEIID-4835 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3, 8.12.x-6.4 > > > The original implementation of the usage table did not implement the ElementName column. Additional logic will be needed in the metadatavalidator to determine what contributes to the column. -- 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 Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5132?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-5132: ------------------------------- Fix Version/s: 8.12.x-6.4 > 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)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5137) SystemAdmin.usage column dependency issue

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5137?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-5137: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1500505 Bugzilla Update: Perform > SystemAdmin.usage column dependency issue > ----------------------------------------- > > Key: TEIID-5137 > URL: https://issues.jboss.org/browse/TEIID-5137 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.12.x-6.4, 9.3.5, 10.1, 10.0.1 > > > For "object_type" == "Column", the field "Name" should be the name of the table. > Here it is the same value of "ElementName" fields (ie column name). > {code} > { > "VDBName" => "Financials", > "UID" => "tid:252cb13c7440-0c0428eb-0000000d", > "object_type" => "Column", > "SchemaName" => "ACCOUNTHOLDINGS", > "Name" => "PRODUCTID", > "ElementName" => "PRODUCTID", > "Uses_UID" => "tid:694b1432214b-cbf6d637-0000000d", > "Uses_object_type" => "Column", > "Uses_SchemaName" => "EU_Customers_EDL", > "Uses_Name" => "ACCOUNTHOLDINGS", > "Uses_ElementName" => "PRODUCTID" > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5137) SystemAdmin.usage column dependency issue

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5137?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-5137: ------------------------------- Fix Version/s: 8.12.x-6.4 > SystemAdmin.usage column dependency issue > ----------------------------------------- > > Key: TEIID-5137 > URL: https://issues.jboss.org/browse/TEIID-5137 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.12.x-6.4, 9.3.5, 10.1, 10.0.1 > > > For "object_type" == "Column", the field "Name" should be the name of the table. > Here it is the same value of "ElementName" fields (ie column name). > {code} > { > "VDBName" => "Financials", > "UID" => "tid:252cb13c7440-0c0428eb-0000000d", > "object_type" => "Column", > "SchemaName" => "ACCOUNTHOLDINGS", > "Name" => "PRODUCTID", > "ElementName" => "PRODUCTID", > "Uses_UID" => "tid:694b1432214b-cbf6d637-0000000d", > "Uses_object_type" => "Column", > "Uses_SchemaName" => "EU_Customers_EDL", > "Uses_Name" => "ACCOUNTHOLDINGS", > "Uses_ElementName" => "PRODUCTID" > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 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: --------------------------------------- We'll need to see a thread dump from when this is occurring and a general description of the number of vdbs that deployed and how may sources need to have metadata retrieved. > 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 > > 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)

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