November 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4290) Rollback to savepoint should be a no op

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4290?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4290: ---------------------------------- Fix Version/s: 8.12.x-6.4 > Rollback to savepoint should be a no op > --------------------------------------- > > Key: TEIID-4290 > URL: https://issues.jboss.org/browse/TEIID-4290 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.13.6, 9.0.1, 8.12.x-6.4 > > > Save points are not supported and the creation of a save point by an ODBC client is effectively ignored, but the rollback is treated as a full rollback of the transaction. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4290) Rollback to savepoint should be a no op

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4290?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4290. ----------------------------------- Resolution: Done > Rollback to savepoint should be a no op > --------------------------------------- > > Key: TEIID-4290 > URL: https://issues.jboss.org/browse/TEIID-4290 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12.x-6.4, 9.0.1, 8.13.6, 9.1 > > > Save points are not supported and the creation of a save point by an ODBC client is effectively ignored, but the rollback is treated as a full rollback of the transaction. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5164) Infinispan hotrod translator aggregate functions issues

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5164?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-5164: ------------------------------- Fix Version/s: 8.12.x-6.4 > Infinispan hotrod translator aggregate functions issues > ------------------------------------------------------- > > Key: TEIID-5164 > URL: https://issues.jboss.org/browse/TEIID-5164 > Project: Teiid > Issue Type: Bug > Components: JDG Connector, Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > Fix For: 8.12.x-6.4 > > > Aggregate functions doesn't work with infinispan hotrod translator. > Example: > {code:sql} > SELECT AVG(IntnUM) FROM BQT1.SmallA > {code} > results in > {code} > 12:07:57,882 ERROR [org.teiid.CONNECTOR] (Worker2_QueryProcessorQueue70) Connector worker process failed for atomic-request=+VUUR2vieWhT.20.1.10: java.lang.AssertionError: Inproper results returned. Expected 1 columns, but was 0 > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:439) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:236) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_151] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_151] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_151] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at com.sun.proxy.$Proxy79.more(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:309) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_151] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_151] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_151] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151] > 12:07:57,888 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue71) TEIID30020 Processing exception for request +VUUR2vieWhT.20 'TEIID30504 jdg7-source: Inproper results returned. Expected 1 columns, but was 0'. Originally TeiidProcessingException ConnectorWorkItem.java:439. Enable more detailed logging to see the entire stacktrace. > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5157) Quickstart dynamicvdb-dataroles need to force deploy vdb

by Jan Stastny (JIRA)

[ https://issues.jboss.org/browse/TEIID-5157?page=com.atlassian.jira.plugin... ] Jan Stastny commented on TEIID-5157: ------------------------------------ It would be best to rename the vdb. Because this quickstart affects the prerequisite fulfillment for the others. (Many quickstarts depend on Portfolio vdb, but not on this one, but the one from dynamicvdb-datafederation quickstart). > Quickstart dynamicvdb-dataroles need to force deploy vdb > -------------------------------------------------------- > > Key: TEIID-5157 > URL: https://issues.jboss.org/browse/TEIID-5157 > Project: Teiid > Issue Type: Bug > Components: Quick Starts > Affects Versions: 8.12.x-6.4 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Blocker > > if dynamicvdb-datafederation run first, need to add force redeploy during vdb deploy: > {code} > deploy ../quickstarts/dynamicvdb-dataroles/src/vdb/portfolio-vdb.xml > {code} > vs. > {code} > deploy --force ../quickstarts/dynamicvdb-dataroles/src/vdb/portfolio-vdb.xml > {code} > Otherwise the vdb is not redeployed and user works with the old one. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3843) SAP HANA wrong results from MOD with float argument

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3843?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3843: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1284878|https://bugzilla.redhat.com/show_bug.cgi?id=1284878] from ON_QA to ASSIGNED > SAP HANA wrong results from MOD with float argument > --------------------------------------------------- > > Key: TEIID-3843 > URL: https://issues.jboss.org/browse/TEIID-3843 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.2.6_2 > Reporter: Jan Stastny > Assignee: Ted Jones > > SAP HANA doesn't handle correctly MOD function with float arguments. The problem occurs when the float value is less than zero. > According to SAP HANA documentation, its MOD implementation follows the symmetric handling of MOD on less than zero values. In such case, the resulting value should be computed as: > a is negative whole number > n is positive whole number > mod(a,n) > # get -1*a > # compute mod(-1*a,n) > # multiply the result by -1 > # result is -1*mod(-1*a,n) > SAP HANA follows this rule for other numeric types than float. For example for Long value -24 MOD(-24,11)=-2 , which is correct according to the MOD definition. > But when you call MOD(-24.0,11) you get 2.0 > In current state, the only thing Teiid could do is to prevent pushing MOD with float arguments. It helps to cast explicitly the column to double. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4845) Google translator comparison with boolean value matches all rows

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4845?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4845: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1515145|https://bugzilla.redhat.com/show_bug.cgi?id=1515145] from NEW to MODIFIED > Google translator comparison with boolean value matches all rows > ---------------------------------------------------------------- > > Key: TEIID-4845 > URL: https://issues.jboss.org/browse/TEIID-4845 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.10.6_3 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.3, 8.12.x-6.4, 9.2.2 > > > Both following queries match and remove all rows (ie. with both true/false/null values): > DELETE WHERE BooleanValue > DELETE WHERE NOT BooleanValue > Where column in foreign table is: > booleanvalue boolean OPTIONS (NATIVE_TYPE 'BOOLEAN') > and view: > BooleanValue boolean -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5167) PrestoDB translator - NULL values are not allowed on the probe side of SemiJoin operator

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5167?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-5167: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1515761 Bugzilla Update: Perform > PrestoDB translator - NULL values are not allowed on the probe side of SemiJoin operator > ---------------------------------------------------------------------------------------- > > Key: TEIID-5167 > URL: https://issues.jboss.org/browse/TEIID-5167 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 8.12.x-6.4 > Reporter: Andrej Šmigala > Assignee: Steven Hawkins > > When running queries containg a subquery such as > {code:sql} > SELECT INTKEY, DOUBLENUM FROM BQT1.SMALLA WHERE DOUBLENUM <> ALL (SELECT DOUBLENUM FROM BQT1.SMALLA WHERE INTKEY = 40) > {code} > An exception is thrown: > {noformat} > org.teiid.translator.TranslatorException: Unexpected exception while translating results: Query failed (#20171121_103829_00016_8zhqn): NULL values are not allowed on the probe side of SemiJoin operator. See the query plan for details. > at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:351) [translator-jdbc-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:433) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:236) > 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.$Proxy80.more(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:309) > 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] > Caused by: java.sql.SQLException: Query failed (#20171121_103829_00016_8zhqn): NULL values are not allowed on the probe side of SemiJoin operator. See the query plan for details. > at com.facebook.presto.jdbc.PrestoResultSet.resultsException(PrestoResultSet.java:1799) > at com.facebook.presto.jdbc.PrestoResultSet$ResultsPageIterator.computeNext(PrestoResultSet.java:1787) > at com.facebook.presto.jdbc.PrestoResultSet$ResultsPageIterator.computeNext(PrestoResultSet.java:1756) > at com.facebook.presto.jdbc.internal.guava.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:145) > at com.facebook.presto.jdbc.internal.guava.collect.AbstractIterator.hasNext(AbstractIterator.java:140) > at com.facebook.presto.jdbc.internal.guava.collect.TransformedIterator.hasNext(TransformedIterator.java:42) > at com.facebook.presto.jdbc.internal.guava.collect.MultitransformedIterator.hasNext(MultitransformedIterator.java:50) > at com.facebook.presto.jdbc.internal.guava.collect.MultitransformedIterator.hasNext(MultitransformedIterator.java:50) > at com.facebook.presto.jdbc.PrestoResultSet.next(PrestoResultSet.java:149) > at org.jboss.jca.adapters.jdbc.WrappedResultSet.next(WrappedResultSet.java:1862) > at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:338) [translator-jdbc-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] > ... 19 more > {noformat} > The query is translated as > {code:sql} > SELECT g_0.intkey AS c_0, g_0.doublenum AS c_1 FROM smalla AS g_0 WHERE g_0.doublenum NOT IN (SELECT g_1.doublenum FROM smalla AS g_1 WHERE g_1.intkey = 40) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 commented on TEIID-5007: --------------------------------------- > I am guessing that will work for Teiid. What I thought you were getting at was using as a reference is https://github.com/jboss-openshift/openshift-examples/blob/master/hellowo... Which then requires adding in the module for KUBE_PING support. I thought there would be a wildfly image with support already there and change our image to layer on it, but I haven't found one yet. The official images https://github.com/openshift-s2i/s2i-wildfly/tree/master/11.0 don't seem to have anything for ha. > we need to use same stack as "kubernates" which looks same as in clustered.xml What are you referring to? > 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)

8 years, 4 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5007?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5007: ------------------------------------- so, we need to use same stack as "kubernates" which looks same as in clustered.xml. I am guessing that will work for Teiid. > 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)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5149) Infinispan-hotrod translator used cache name 'default' as a default value, when it may not be configured

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5149?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-5149: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1513730|https://bugzilla.redhat.com/show_bug.cgi?id=1513730] from NEW to ASSIGNED > Infinispan-hotrod translator used cache name 'default' as a default value, when it may not be configured > -------------------------------------------------------------------------------------------------------- > > Key: TEIID-5149 > URL: https://issues.jboss.org/browse/TEIID-5149 > Project: Teiid > Issue Type: Bug > Components: JDG Connector > Affects Versions: 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Ramesh Reddy > > A JDG server was configured so that only the needed caches be configured, which included removing the 'default' cache. It was then determined that there was an issue with Teiid integrating with a JDG, because the default cache is referenced and causes a failure. > Did notice in the ProtobufMetadataProcessor that the default value for "cacheName" is 'default'. So this maybe where the possible problem is. -- 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