[JBoss JIRA] (TEIID-5006) NPE when querying RAR description
by Andrej Šmigala (JIRA)
Andrej Šmigala created TEIID-5006:
-------------------------------------
Summary: NPE when querying RAR description
Key: TEIID-5006
URL: https://issues.jboss.org/browse/TEIID-5006
Project: Teiid
Issue Type: Bug
Components: JDG Connector
Affects Versions: 8.12.x-6.4
Reporter: Andrej Šmigala
Assignee: Steven Hawkins
When running the read-rar-description on the infinispan-hotrod resource adapter, a NPE is logged in the server log:
{noformat}
10:59:10,245 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014612: Operation ("read-rar-description") failed - address: ([("subsystem" => "teiid")]): java.lang.NullPointerException
at org.teiid.deployers.ExtendedPropertyMetadata.addProperty(ExtendedPropertyMetadata.java:119)
at org.teiid.deployers.ExtendedPropertyMetadata.<init>(ExtendedPropertyMetadata.java:105)
at org.teiid.jboss.ReadRARDescription.buildNode(TeiidOperationHandler.java:1613)
at org.teiid.jboss.ReadRARDescription.executeOperation(TeiidOperationHandler.java:1583)
at org.teiid.jboss.ReadRARDescription.executeOperation(TeiidOperationHandler.java:1543)
at org.teiid.jboss.BaseOperationHandler$1.execute(BaseOperationHandler.java:79)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:710) [jboss-as-controller-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:545) [jboss-as-controller-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:338) [jboss-as-controller-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:314) [jboss-as-controller-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1152) [jboss-as-controller-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:335) [jboss-as-controller-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:204) [jboss-as-controller-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:209) [jboss-as-controller-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136) [jboss-as-controller-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158) [jboss-as-controller-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:154) [jboss-as-controller-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0_131]
at javax.security.auth.Subject.doAs(Subject.java:422) [rt.jar:1.8.0_131]
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [jboss-as-controller-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:154) [jboss-as-controller-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:364) [jboss-as-protocol-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:473) [jboss-as-protocol-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]
{noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 5 months
[JBoss JIRA] (TEIID-4924) Push Teiid artifacts to maven central
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4924?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4924:
-------------------------------------
I went through most of the projects and updated their Maven coordinates. wildfly-swarm needs more attention but may be not related to this. Also updated couple references in the document in in the archtypes section.
I did not see any reason to modify the JBoss modules names, the main aim was with frameworks that are using the maven directly like spring-boot and wildfly-swarm. If there is an issue when we check the wildfly-swarm stuff we will reconsider this, as this will touch lot more in terms of documents and scripts etc.
I did find that 10.0.0.Alpha2 version did not build the jdbc and admin jar, I corrected it now.
If there are no more issues I ready to resolve this.
> Push Teiid artifacts to maven central
> -------------------------------------
>
> Key: TEIID-4924
> URL: https://issues.jboss.org/browse/TEIID-4924
> Project: Teiid
> Issue Type: Sub-task
> Reporter: Kylin Soong
> Assignee: Ramesh Reddy
> Fix For: 10.0
>
>
> Prepare to push teiis-spring-boot to maven central.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 5 months
[JBoss JIRA] (TEIID-4918) Enhance infinispan support for muti-threaded puts or using putAll
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4918?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4918:
---------------------------------------
> The next issue is doing these operations atomically which I do not think I have a good thought process yet.
>From the infinispan api it implies that the put all operations are synthetic and thus not atomic. On the Teiid side we don't need the operation to be atomic - however as we would expect a wrapping transaction to be honored when needed (once it's supported by infinispan).
> Meanwhile, I did put in enhancement using PutAll method. When the table is empty if one issues a "insert into ... select" it will execute a "bulk" insert into translator, which will use "putAll" which should improve performance
This would apply to the first batch sent to the translator. Subsequent batches would see the target as non-empty.
Without locking this does have a consistency issue - if another insert happens at the same time, you won't be empty any longer for the putAll. The same is true in a narrow sense for the individual inserts - it's a best effort consistency.
Another concern is that we're not checking the pk constraint for the insert - so a putAll if there is a duplicate would result in the last entry being respected, rather than an exception in an insert scenario.
> Enhance infinispan support for muti-threaded puts or using putAll
> -----------------------------------------------------------------
>
> Key: TEIID-4918
> URL: https://issues.jboss.org/browse/TEIID-4918
> Project: Teiid
> Issue Type: Enhancement
> Components: Infinispan
> Affects Versions: 9.3, 8.12.x-6.4
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Fix For: 10.0
>
>
> For performance reasons, it was requested that the infinispan connector/translator be enhanced to be multi-threaded when doing batch inserts or try using the putAll option.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 5 months
[JBoss JIRA] (TEIID-4994) For materialization, use "Ignore return values" option to improve performance
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4994?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-4994.
---------------------------------
Resolution: Won't Fix
TEIID-4918 should improve performance in materialization case, this changes the behavior of the existing translator, so it will not be considered for now.
> For materialization, use "Ignore return values" option to improve performance
> -----------------------------------------------------------------------------
>
> Key: TEIID-4994
> URL: https://issues.jboss.org/browse/TEIID-4994
> Project: Teiid
> Issue Type: Enhancement
> Components: Infinispan
> Affects Versions: 8.12.x-6.4, 9.3.2
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Fix For: 10.0
>
>
> For a performance improvement, change to use Flag.IGNORE_RETURN_VALUES
> Cache noPreviousValueCache = cache.getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES);
> noPreviousValueCache.put(k, v);
> or can use ConfigurationBuilder settings:
> ConfigurationBuilder cb = new ConfigurationBuilder();
> cb.unsafe().unreliableReturnValues(true);
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 5 months
[JBoss JIRA] (TEIID-4918) Enhance infinispan support for muti-threaded puts or using putAll
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4918?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-4918.
---------------------------------
Resolution: Done
The remote execution of the UDF framework is in, but working with Protostream Marshaller feature is not available yet. See [1]. So, remote execution is troublesome and may need Infinispan folks help to find any hack.
Meanwhile, I did put in enhancement using PutAll method. When the table is empty if one issues a "insert into ... select" it will execute a "bulk" insert into translator, which will use "putAll" which should improve performance. Note, this is primary usage in 6.4, where truncate and load happens for materialization.
Remote execution needs to be revisited at later date.
[1] https://issues.jboss.org/browse/ISPN-8020
> Enhance infinispan support for muti-threaded puts or using putAll
> -----------------------------------------------------------------
>
> Key: TEIID-4918
> URL: https://issues.jboss.org/browse/TEIID-4918
> Project: Teiid
> Issue Type: Enhancement
> Components: Infinispan
> Affects Versions: 9.3, 8.12.x-6.4
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Fix For: 10.0
>
>
> For performance reasons, it was requested that the infinispan connector/translator be enhanced to be multi-threaded when doing batch inserts or try using the putAll option.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 5 months
[JBoss JIRA] (TEIID-4994) For materialization, use "Ignore return values" option to improve performance
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4994?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4994:
-------------------------------------
One can not turn off for materialization and keep it for others.
> For materialization, use "Ignore return values" option to improve performance
> -----------------------------------------------------------------------------
>
> Key: TEIID-4994
> URL: https://issues.jboss.org/browse/TEIID-4994
> Project: Teiid
> Issue Type: Enhancement
> Components: Infinispan
> Affects Versions: 8.12.x-6.4, 9.3.2
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Fix For: 10.0
>
>
> For a performance improvement, change to use Flag.IGNORE_RETURN_VALUES
> Cache noPreviousValueCache = cache.getAdvancedCache().withFlags(Flag.IGNORE_RETURN_VALUES);
> noPreviousValueCache.put(k, v);
> or can use ConfigurationBuilder settings:
> ConfigurationBuilder cb = new ConfigurationBuilder();
> cb.unsafe().unreliableReturnValues(true);
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 5 months
[JBoss JIRA] (TEIID-5005) Boolean expression is incorrectly rewritten in WHERE condition and causes errors on PG
by dalex dalex (JIRA)
[ https://issues.jboss.org/browse/TEIID-5005?page=com.atlassian.jira.plugin... ]
dalex dalex commented on TEIID-5005:
------------------------------------
[~shawkins] great! thx a lot for the quick fix.
> Boolean expression is incorrectly rewritten in WHERE condition and causes errors on PG
> --------------------------------------------------------------------------------------
>
> Key: TEIID-5005
> URL: https://issues.jboss.org/browse/TEIID-5005
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.3.1
> Environment: teiid-9.3.1 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 10.0, 9.2.5, 9.3.2
>
>
> when running the following query on PG:
> {code:sql}
> select * from test_pg.test_bool_exps where ((b=true) and (a=1)) = true ;;
> {code}
> teiid returns the following error:
> {code}
> 2017-07-25 13:19:10,211 WARN [org.teiid.CONNECTOR] (Worker5_QueryProcessorQueue329) o4ihy1GzEdYV Connector worker process failed for atomic-request=o4ihy1GzEdYV.89.0.71: org.teiid.t
> ranslator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."a" AS c_0, g_0."b" AS c_1 FROM "public"."test_bool_
> exps" AS g_0 WHERE g_0."b" = TRUE AND g_0."a" = 1 = TRUE LIMIT 100]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:365)
> at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:220)
> at com.sun.proxy.$Proxy28.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)
> 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:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> though the same query on MySQL, MSSQL and Oracle works correctly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 5 months
[JBoss JIRA] (TEIID-5005) Boolean expression is incorrectly rewritten in WHERE condition and causes errors on PG
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5005?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5005.
-----------------------------------
Fix Version/s: 10.0
9.2.5
9.3.2
Resolution: Done
Expanded the previous fix to all conditions.
> Boolean expression is incorrectly rewritten in WHERE condition and causes errors on PG
> --------------------------------------------------------------------------------------
>
> Key: TEIID-5005
> URL: https://issues.jboss.org/browse/TEIID-5005
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.3.1
> Environment: teiid-9.3.1 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 10.0, 9.2.5, 9.3.2
>
>
> when running the following query on PG:
> {code:sql}
> select * from test_pg.test_bool_exps where ((b=true) and (a=1)) = true ;;
> {code}
> teiid returns the following error:
> {code}
> 2017-07-25 13:19:10,211 WARN [org.teiid.CONNECTOR] (Worker5_QueryProcessorQueue329) o4ihy1GzEdYV Connector worker process failed for atomic-request=o4ihy1GzEdYV.89.0.71: org.teiid.t
> ranslator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."a" AS c_0, g_0."b" AS c_1 FROM "public"."test_bool_
> exps" AS g_0 WHERE g_0."b" = TRUE AND g_0."a" = 1 = TRUE LIMIT 100]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:365)
> at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:220)
> at com.sun.proxy.$Proxy28.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)
> 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:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> though the same query on MySQL, MSSQL and Oracle works correctly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 5 months
[JBoss JIRA] (TEIID-5005) Boolean expression is incorrectly rewritten in WHERE condition and causes errors on PG
by dalex dalex (JIRA)
[ https://issues.jboss.org/browse/TEIID-5005?page=com.atlassian.jira.plugin... ]
dalex dalex updated TEIID-5005:
-------------------------------
Summary: Boolean expression is incorrectly rewritten in WHERE condition and causes errors on PG (was: Boolean expression is incorrectly rewritten in WHERE condition and cause errors on PG)
> Boolean expression is incorrectly rewritten in WHERE condition and causes errors on PG
> --------------------------------------------------------------------------------------
>
> Key: TEIID-5005
> URL: https://issues.jboss.org/browse/TEIID-5005
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.3.1
> Environment: teiid-9.3.1 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Blocker
>
> when running the following query on PG:
> {code:sql}
> select * from test_pg.test_bool_exps where ((b=true) and (a=1)) = true ;;
> {code}
> teiid returns the following error:
> {code}
> 2017-07-25 13:19:10,211 WARN [org.teiid.CONNECTOR] (Worker5_QueryProcessorQueue329) o4ihy1GzEdYV Connector worker process failed for atomic-request=o4ihy1GzEdYV.89.0.71: org.teiid.t
> ranslator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."a" AS c_0, g_0."b" AS c_1 FROM "public"."test_bool_
> exps" AS g_0 WHERE g_0."b" = TRUE AND g_0."a" = 1 = TRUE LIMIT 100]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:365)
> at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:220)
> at com.sun.proxy.$Proxy28.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)
> 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:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> though the same query on MySQL, MSSQL and Oracle works correctly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 5 months
[JBoss JIRA] (TEIID-5005) Boolean expression is incorrectly rewritten in WHERE condition and cause errors on PG
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5005?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5005:
---------------------------------------
The fix for TEIID-4877 was too narrow. We need to nest more expression types in parens to satisfy the pg parser.
> Boolean expression is incorrectly rewritten in WHERE condition and cause errors on PG
> -------------------------------------------------------------------------------------
>
> Key: TEIID-5005
> URL: https://issues.jboss.org/browse/TEIID-5005
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.3.1
> Environment: teiid-9.3.1 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Blocker
>
> when running the following query on PG:
> {code:sql}
> select * from test_pg.test_bool_exps where ((b=true) and (a=1)) = true ;;
> {code}
> teiid returns the following error:
> {code}
> 2017-07-25 13:19:10,211 WARN [org.teiid.CONNECTOR] (Worker5_QueryProcessorQueue329) o4ihy1GzEdYV Connector worker process failed for atomic-request=o4ihy1GzEdYV.89.0.71: org.teiid.t
> ranslator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."a" AS c_0, g_0."b" AS c_1 FROM "public"."test_bool_
> exps" AS g_0 WHERE g_0."b" = TRUE AND g_0."a" = 1 = TRUE LIMIT 100]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:365)
> at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:220)
> at com.sun.proxy.$Proxy28.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)
> 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:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> though the same query on MySQL, MSSQL and Oracle works correctly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 5 months