June 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3534) Infinispan-dsl-cache translator: can't insert null into column of type boolean

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3534?page=com.atlassian.jira.plugin... ] Van Halbert closed TEIID-3534. ------------------------------ Resolution: Rejected It has been determined that this is a JDG issue. The possible work arounds are: - assign defaults in the proto def file - or always pass a value for the boolean column > Infinispan-dsl-cache translator: can't insert null into column of type boolean > ------------------------------------------------------------------------------ > > Key: TEIID-3534 > URL: https://issues.jboss.org/browse/TEIID-3534 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Filip Elias > Assignee: Van Halbert > Attachments: server.log, testVDB.vdb > > > Inserting null into boolean column causes exception. > Sample queries: > {code} > insert into smalla(intKey, stringKey,booleanValue) values(128,'ss',null); > insert into smalla(intKey, stringKey) values(128,'ss'); > {code} > This query works: > {code} > insert into smalla(intKey, stringKey,booleanValue) values(128,'ss',false); > {code} > Exception: > {code} > Connector worker process failed for atomic-request=NuZ8Nt3h1bKx.52.0.44: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message id[239] returned server error (status=0x85): org.hibernate.search.bridge.BridgeException: Exception while calling bridge#set > class: org.infinispan.query.remote.indexing.ProtobufValueWrapper > path: > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:298) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:88) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:74) > at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56) > {code} > This bug breaks data integrity. If this exception is thrown, data will be inserted but it won't be indexed. > The whole exception is in the attachment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3556) BufferManager reserve memory variable is decremented twice

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3556?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3556: ------------------------------------------------ Anne-Louise Tangring <atangrin(a)redhat.com> changed the Status of [bug 1234839|https://bugzilla.redhat.com/show_bug.cgi?id=1234839] from NEW to MODIFIED > BufferManager reserve memory variable is decremented twice > ---------------------------------------------------------- > > Key: TEIID-3556 > URL: https://issues.jboss.org/browse/TEIID-3556 > Project: Teiid > Issue Type: Bug > Components: Server > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.7.1.6_2, 8.12, 8.11.1 > > > Web admin console shows negative value for Memory Used By Active Plans(KB) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3553) Odata - if table name is ambiguous, teiid returns result from first table

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3553?page=com.atlassian.jira.plugin... ] Van Halbert reopened TEIID-3553: -------------------------------- > Odata - if table name is ambiguous, teiid returns result from first table > ------------------------------------------------------------------------- > > Key: TEIID-3553 > URL: https://issues.jboss.org/browse/TEIID-3553 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12 > > > If table name is ambiguous, teiid returns data from first matching table. I expect, that it should return error message similar to exception which is thrown via JDBC. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3553) Odata - if table name is ambiguous, teiid returns result from first table

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3553?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3553: ------------------------------- Fix Version/s: 8.7.1.6_2 > Odata - if table name is ambiguous, teiid returns result from first table > ------------------------------------------------------------------------- > > Key: TEIID-3553 > URL: https://issues.jboss.org/browse/TEIID-3553 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.12 > > > If table name is ambiguous, teiid returns data from first matching table. I expect, that it should return error message similar to exception which is thrown via JDBC. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3557) Can't reload VDB in domain mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3557?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3557: ------------------------------------------------ Anne-Louise Tangring <atangrin(a)redhat.com> changed the Status of [bug 1234822|https://bugzilla.redhat.com/show_bug.cgi?id=1234822] from NEW to MODIFIED > Can't reload VDB in domain mode > ------------------------------- > > Key: TEIID-3557 > URL: https://issues.jboss.org/browse/TEIID-3557 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.7.1.6_2, 8.12, 8.11.1 > > > Can't reload VDB in domain mode, get the following error: > Server throws the following exception: > [Server:server-one] 12:26:45,678 ERROR [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40088 Could not replicate object org.teiid.query.tempdata.GlobalTableStoreImpl@4e6c9a30: java.lang.IllegalStateException: cluster 'ModeShape.1' is already connected to singleton transport: [dummy-1435055090515, loopback.1, ModeShape.1, loopback-dynamic.1, $TEIID_BM$, dummy-1435055090188, dummy-1435055205654, $TEIID_ED$, teiid-cache, ddl2-vdb.1] > [Server:server-one] at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:919) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] > [Server:server-one] at org.jgroups.JChannel.startStack(JChannel.java:827) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] > [Server:server-one] at org.jgroups.JChannel._preConnect(JChannel.java:525) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] > [Server:server-one] at org.jgroups.JChannel.connect(JChannel.java:277) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] > [Server:server-one] at org.jgroups.JChannel.connect(JChannel.java:268) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] > [Server:server-one] at org.teiid.replication.jgroups.JGroupsObjectReplicator.replicate(JGroupsObjectReplicator.java:563) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.deployers.CompositeGlobalTableStore.createInstance(CompositeGlobalTableStore.java:57) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.jboss.VDBService$1.finishedDeployment(VDBService.java:156) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.deployers.VDBRepository.notifyFinished(VDBRepository.java:352) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.deployers.VDBRepository.finishDeployment(VDBRepository.java:308) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.runtime.AbstractVDBDeployer.metadataLoaded(AbstractVDBDeployer.java:202) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.jboss.VDBService.access$1100(VDBService.java:85) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.jboss.VDBService$6.run(VDBService.java:411) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.jboss.VDBService$7.run(VDBService.java:442) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > [Server:server-one] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:122) > VDB reload works fine in standalone mode. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3558) Duplicate records being for formed for Internal Materialized View cluster

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3558?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3558: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1236604 > Duplicate records being for formed for Internal Materialized View cluster > ------------------------------------------------------------------------- > > Key: TEIID-3558 > URL: https://issues.jboss.org/browse/TEIID-3558 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Pranav K > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7.1.6_2, 8.12, 8.11.1 > > > -On running a query over one of the nodes of a cluster (say node A) to fetch 25000 records (with internal materialization switched on), the cache gets formed on node A and presumably gets synced using the JgroupsObjectReplicator. > -On running the same query on the cache formed in the other node (node B), I noticed that I was getting 25600 records. > -On analysis the records, I saw there were only 1024 distinct records each of which repeated 25 times. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3039) Add support for odata expand

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3039?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3039: ------------------------------------ V4 supports it, but doesn't Teiid need to do something to enable it? > Add support for odata expand > ---------------------------- > > Key: TEIID-3039 > URL: https://issues.jboss.org/browse/TEIID-3039 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Steven Hawkins > Fix For: 8.12 > > > We should add support for odata expand. This can be done with logic similar to the xml document model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3549) Join conditions with OR generate a wrong JDBC query

by Mark Tawk (JIRA)

[ https://issues.jboss.org/browse/TEIID-3549?page=com.atlassian.jira.plugin... ] Mark Tawk commented on TEIID-3549: ---------------------------------- The fix solved the problem Thank you > Join conditions with OR generate a wrong JDBC query > --------------------------------------------------- > > Key: TEIID-3549 > URL: https://issues.jboss.org/browse/TEIID-3549 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Reporter: Mark Tawk > Assignee: Steven Hawkins > Fix For: 8.12 > > > I'm using Teiid 8.10 with h2 translator > I have the following query containing a join with conditions separated by OR logical operator: > select "BilanBanque"."SIGNEDDATA" as "CalculatedField1" > from "implify_data"."Evolution_PCy_050615" "Evolution_PCy_050615" > LEFT JOIN "implify_data"."Evolution_PCy_050615" "MidCat" ON "Evolution_PCy_050615"."ID" = "MidCat"."PID" AND ( ( ("MidCat"."Level" IN (1) ) ) ) > LEFT JOIN "implify_data"."Evolution_PCy_050615" "Data" ON ( ( ("Data"."Level" IN (2) ) ) AND ( ("Data"."PID" = "Evolution_PCy_050615"."ID") OR ("Data"."PID" = "MidCat"."ID") ) ) > LEFT JOIN "implify_data"."Sheet1_haU_010615" "BilanBanque" ON "Data"."ID" = "BilanBanque"."Account" > where ("BilanBanque"."BankName" IN ('Bank1') ) > The corresponding JDBC query executed by Teiid contains 2 times ON after the join: > SELECT g_3."SIGNEDDATA" FROM "implify_data"."Evolution_PCy_050615" AS g_0 LEFT OUTER JOIN "implify_data"."Evolution_PCy_050615" AS g_1 ON g_0."ID" = g_1."PID" AND g_1."Level" = 1 INNER JOIN "implify_data"."Evolution_PCy_050615" AS g_2 INNER JOIN "implify_data"."Sheet1_haU_010615" AS g_3 ON g_2."ID" = g_3."Account" ON g_2."PID" = g_0."ID" OR g_2."PID" = g_1."ID" WHERE g_2."Level" = 2 AND g_3."BankName" = 'Bank1' > if I remove the conditions with OR from the join, the query executes with success. > You find below the execution plan: > <?xml version='1.0' encoding='UTF-8'?><node name="AccessNode"><property name="Relational Node ID"><value>0</value></property><property name="Output Columns"><value>CalculatedField1 (bigdecimal)</value></property><property name="Statistics"><value>Node Output Rows: 0</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 16</value><value>Node Cumulative Process Time: 0</value><value>Node Next Batch Calls: 1</value><value>Node Blocks: 1</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Query"><value>SELECT g_3.SIGNEDDATA FROM (implify_dataModel.implify_data.Evolution_PCy_050615 AS g_0 LEFT OUTER JOIN implify_dataModel.implify_data.Evolution_PCy_050615 AS g_1 ON g_0.ID = g_1.PID AND g_1.Level = 1) INNER JOIN (implify_dataModel.implify_data.Evolution_PCy_050615 AS g_2 INNER JOIN implify_dataModel.implify_data.Sheet1_haU_010615 AS g_3 ON g_2.ID = g_3.Account) ON ((g_2.PID = g_0.ID) OR (g_2.PID = g_1.ID)) WHERE (g_2.Level = 2) AND (g_3.BankName = 'Bank1')</value></property><property name="Model Name"><value>implify_dataModel</value></property><property name="Data Bytes Sent"><value>0</value></property></node> -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3532) Infinispan-dsl-cache translator: Exception is thrown when order by clause is used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3532?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3532: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1232169|https://bugzilla.redhat.com/show_bug.cgi?id=1232169] from NEW to MODIFIED > Infinispan-dsl-cache translator: Exception is thrown when order by clause is used > --------------------------------------------------------------------------------- > > Key: TEIID-3532 > URL: https://issues.jboss.org/browse/TEIID-3532 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Filip Elias > Assignee: Van Halbert > Attachments: server.log > > > Infinispan-dsl-cache translator will fail if order by clause is pushed down. > Sample query: > {code} > select intKey from smalla where intkey > 1 order by intKey > {code} > Exception: > {code} > Connector worker process failed for atomic-request=iLuNd1gO/2N0.4.0.7: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message id[38] returned server error (status=0x85): org.hibernate.hql.ParsingException: HQLPARSER000002: The query FROM org.jboss.qe.jdg_remote.protobuf.SmallA _gen0 WHERE _gen0.intKey > 1 ORDER BY _gen0.null ASC is not valid; Parser error messages: [[statement, statementElement, selectStatement, orderByClause, sortSpecification, sortKey, concatenation, additiveExpression, multiplyExpression, unaryExpression, atom, identPrimary]: line 1:89 mismatched token: [@32,89:92='null',<124>,1:89]; expecting type IDENTIFIER]. > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:298) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:88) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:74) > {code} > Full log is in the attachment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3535) Infinispan-dsl-cache translator: NPE when inserting data if a table doesn't have primary key defined

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3535?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3535: ------------------------------------ Needed to add a null check for PK. > Infinispan-dsl-cache translator: NPE when inserting data if a table doesn't have primary key defined > ---------------------------------------------------------------------------------------------------- > > Key: TEIID-3535 > URL: https://issues.jboss.org/browse/TEIID-3535 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Filip Elias > Assignee: Van Halbert > > Exception: > {code} > ERROR [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue194) Connector worker process failed for atomic-request=ziNYENHc9zCz.0.0.33: java.lang.NullPointerException > at org.teiid.translator.infinispan.dsl.InfinispanUpdateExecution.handleInsert(InfinispanUpdateExecution.java:149) > at org.teiid.translator.infinispan.dsl.InfinispanUpdateExecution.execute(InfinispanUpdateExecution.java:107) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:358) [teiid-engine-8.7.1.6_2-redhat-1.jar:8.7.1.6_2-redhat-1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:325) [teiid-engine-8.7.1.6_2-redhat-1.jar:8.7.1.6_2-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.7.1.6_2-redhat-1.jar:8.7.1.6_2-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.7.1.6_2-redhat-1.jar:8.7.1.6_2-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.7.1.6_2-redhat-1.jar:8.7.1.6_2-redhat-1] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.7.1.6_2-redhat-1.jar:8.7.1.6_2-redhat-1] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.7.1.6_2-redhat-1.jar:8.7.1.6_2-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.7.1.6_2-redhat-1.jar:8.7.1.6_2-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.7.1.6_2-redhat-1.jar:8.7.1.6_2-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2015