September 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4426) More than halt of Teiid's modules have invalid module descriptor (module.xml)

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-4426: ----------------------------------- Summary: More than halt of Teiid's modules have invalid module descriptor (module.xml) Key: TEIID-4426 URL: https://issues.jboss.org/browse/TEIID-4426 Project: Teiid Issue Type: Bug Reporter: Juraj Duráni Assignee: Steven Hawkins More than half of all modules \[1\] in Teiid layer have invalid module.xml file. Each of them states to use XMLNS for module of version 1.0 (_urn:jboss:module:1.0_), but they use _properties_ element, which is available since 1.1. {code:plain|title=\[1\] Affected modules (module:slot)} org.jboss.teiid.translator.hbase:main org.jboss.teiid.translator.simpledb:main org.jboss.teiid.translator.salesforce:main org.jboss.teiid.admin:main org.jboss.teiid.translator.jpa:main org.jboss.teiid.translator.olap:main io.swagger:main org.jboss.teiid.common-core:main com.fasterxml.jackson:main com.fasterxml.jackson.dataformat.yaml:main org.jboss.teiid.translator.cassandra:main org.jboss.teiid.translator.google.api:main com.force.api:22 org.reflections:main org.jboss.teiid.translator.google:main org.antlr:4.5 org.jboss.teiid.translator.jdbc:main org.osgeo.proj4j:main org.apache.xmlbeans:main org.apache.olingo:main com.google.code.findbugs:main org.apache.commons.lang:3.3.2 org.jboss.teiid.translator.simpledb.api:main org.jboss.teiid.translator.mongodb.api:main org.jboss.teiid.api:main org.jboss.teiid.translator.excel:main com.datastax.cassandra.driver.core:main com.fasterxml.aalto-xml:main org.jboss.teiid:main org.jboss.teiid.translator.ldap:main org.jboss.teiid.translator.odata:main com.facebook.presto:main com.vividsolutions.jts:main org.jboss.oreva:main com.fasterxml.jackson.datatype:main nux.nux:main org.jboss.teiid.translator.ws:main org.jboss.teiid.translator.salesforce:34 dom4j:main org.jboss.teiid.translator.object:main org.jboss.teiid.security:main org.jboss.teiid.translator.infinispan.cache:main org.jboss.teiid.translator.hive:main org.jboss.teiid.translator.mongodb:main org.jboss.teiid.olingo.common:main net.sf.saxon:main {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4419) Allow pre-evaluation of uncorrelated scalar subqueries in more circumstances

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4419?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4419: --------------------------------- Fix Version/s: 8.7.9.6_2 > Allow pre-evaluation of uncorrelated scalar subqueries in more circumstances > ---------------------------------------------------------------------------- > > Key: TEIID-4419 > URL: https://issues.jboss.org/browse/TEIID-4419 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.7.9.6_2 > > > In some instances it is better to pre-evaluate uncorrelated scalar subqueries rather than pushing down. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4425) LDAP translator and multi-valued arrays

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4425: ------------------------------------- Summary: LDAP translator and multi-valued arrays Key: TEIID-4425 URL: https://issues.jboss.org/browse/TEIID-4425 Project: Teiid Issue Type: Feature Request Components: LDAP Connector Reporter: Debbie Steigner Assignee: Steven Hawkins Fix For: 8.12 The problem is with how multi-valued attribute from the LDAP response is handled. They don't want to have the data mapped to an array or multivalued-concat and then transformed into another table to get the unique values. There is an issue with the translator as it should handle multivalued attribute, by simply creating multiple rows for each value of the multivalued attribute. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3119) Improve full sort performance for dup removal and grouping

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3119?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-3119. -------------------------------- Resolution: Done > Improve full sort performance for dup removal and grouping > ---------------------------------------------------------- > > Key: TEIID-3119 > URL: https://issues.jboss.org/browse/TEIID-3119 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.6.6_2, 8.9 > > > We perform a full sort for grouping/distinct reusing the existing sorting logic. This is not as efficient as it could for larger data sets with smaller numbers of groups. A hash implementation or combining the grouping with the sorting would perform better. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3119) Improve full sort performance for dup removal and grouping

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3119?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3119: --------------------------------- Fix Version/s: 8.7.6.6_2 > Improve full sort performance for dup removal and grouping > ---------------------------------------------------------- > > Key: TEIID-3119 > URL: https://issues.jboss.org/browse/TEIID-3119 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9, 8.7.6.6_2 > > > We perform a full sort for grouping/distinct reusing the existing sorting logic. This is not as efficient as it could for larger data sets with smaller numbers of groups. A hash implementation or combining the grouping with the sorting would perform better. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3119) Improve full sort performance for dup removal and grouping

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3119?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3119: ---------------------------------- > Improve full sort performance for dup removal and grouping > ---------------------------------------------------------- > > Key: TEIID-3119 > URL: https://issues.jboss.org/browse/TEIID-3119 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > We perform a full sort for grouping/distinct reusing the existing sorting logic. This is not as efficient as it could for larger data sets with smaller numbers of groups. A hash implementation or combining the grouping with the sorting would perform better. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4423) UPDATE command with non-pushdown functions leads to TEIID30253 error

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4423?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4423: --------------------------------------- > so if we have a query with update command and we try to use a non-deterministic function on a field which is not unique (primary key) we will get the TEIID30253 error message because having not unique fields means deterministic behavior. Correct? Nearly. It just matters that there is a unique key at all regardless of whether it is being updated, then each row can be updated individually. > UPDATE command with non-pushdown functions leads to TEIID30253 error > -------------------------------------------------------------------- > > Key: TEIID-4423 > URL: https://issues.jboss.org/browse/TEIID-4423 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.x > Environment: teiid-8.12-Beta1 on Red Hat JBoss Enterprise Application Platform - Version 6.3.0.GA > teiid-9.0.3 on WildFly Full 9.0.2.Final > Reporter: dalex dalex > Assignee: Steven Hawkins > > Running the following queries: > {code:sql} > update test.textagg_test_2 set id =(select uuid());; > {code} > or > {code:sql} > update test.textagg_test_2 set id =(select rand());; > {code} > leads to the following errors: > {code} > TEIID30253 Source UPDATE or DELETE command "UPDATE test.textagg_test_2 SET id = (SELECT uuid() LIMIT 2)" contains non-pushdown constructs and no compensating action can be taken as the table lacks a unique key or the source does not support equality predicates. > {code} > and > {code} > TEIID30253 Source UPDATE or DELETE command "UPDATE test.textagg_test_2 SET id = convert((SELECT rand() LIMIT 2), string)" contains non-pushdown constructs and no compensating action can be taken as the table lacks a unique key or the source does not support equality predicates. > {code} > though the following query: > {code:sql} > update test.textagg_test_2 set id =(select now());; > {code} > works without errors. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4423) UPDATE command with non-pushdown functions leads to TEIID30253 error

by dalex dalex (JIRA)

[ https://issues.jboss.org/browse/TEIID-4423?page=com.atlassian.jira.plugin... ] dalex dalex commented on TEIID-4423: ------------------------------------ [~shawkins] I got it, so if we have a query with update command and we try to use a non-deterministic function on a field which is not unique (primary key) we will get the TEIID30253 error message because having not unique fields means deterministic behavior. Correct? Another way to treat it is to use, for this case, pushdown support for the uuid function like moving the treatment on MySQL level. > In general each database has different rules for handling non-deterministic expressions. We are similar to H2, but it looks like you are expecting Postgres style handling such that uncorrelated subqueries are always treated as deterministic. Didn't know about it. Interesting. > UPDATE command with non-pushdown functions leads to TEIID30253 error > -------------------------------------------------------------------- > > Key: TEIID-4423 > URL: https://issues.jboss.org/browse/TEIID-4423 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.x > Environment: teiid-8.12-Beta1 on Red Hat JBoss Enterprise Application Platform - Version 6.3.0.GA > teiid-9.0.3 on WildFly Full 9.0.2.Final > Reporter: dalex dalex > Assignee: Steven Hawkins > > Running the following queries: > {code:sql} > update test.textagg_test_2 set id =(select uuid());; > {code} > or > {code:sql} > update test.textagg_test_2 set id =(select rand());; > {code} > leads to the following errors: > {code} > TEIID30253 Source UPDATE or DELETE command "UPDATE test.textagg_test_2 SET id = (SELECT uuid() LIMIT 2)" contains non-pushdown constructs and no compensating action can be taken as the table lacks a unique key or the source does not support equality predicates. > {code} > and > {code} > TEIID30253 Source UPDATE or DELETE command "UPDATE test.textagg_test_2 SET id = convert((SELECT rand() LIMIT 2), string)" contains non-pushdown constructs and no compensating action can be taken as the table lacks a unique key or the source does not support equality predicates. > {code} > though the following query: > {code:sql} > update test.textagg_test_2 set id =(select now());; > {code} > works without errors. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4424) Error when factory overrides initCapabilities due WrappedConnection is what Teiid is passing

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4424?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4424. ----------------------------------- Resolution: Done Added the unwrap logic. > Error when factory overrides initCapabilities due WrappedConnection is what Teiid is passing > -------------------------------------------------------------------------------------------- > > Key: TEIID-4424 > URL: https://issues.jboss.org/browse/TEIID-4424 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.1, 9.0.4 > > > The infinispan hotrod translator factory class is trying to override initCapabililties(Connection) but is seeing the following error on the server: > 20:34:22,861 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue5) zLiKTbTSLJkH TEIID30019 Unexpected exception for request zLiKTbTSLJkH.0: java.lang.ClassCastException: org.teiid.resource.spi.WrappedConnection cannot be cast to org.teiid.translator.object.ObjectConnection > at org.teiid.translator.infinispan.hotrod.InfinispanHotRodExecutionFactory.initCapabilities(InfinispanHotRodExecutionFactory.java:53) > at org.teiid.dqp.internal.datamgr.ConnectorManager.buildCapabilities(ConnectorManager.java:186) > at org.teiid.dqp.internal.datamgr.ConnectorManager.getCapabilities(ConnectorManager.java:163) > at org.teiid.dqp.internal.process.CachedFinder.findCapabilities(CachedFinder.java:108) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4423) UPDATE command with non-pushdown functions leads to TEIID30253 error

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4423?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4423: --------------------------------------- > That will force a single value for the uuid function / subquery. Actually that is inconsistent that we currently work that way. The whole expression should still be seen as non-deterministic. In general each database has different rules for handling non-deterministic expressions. We are similar to H2, but it looks like you are expecting Postgres style handling such that uncorrelated subqueries are always treated as deterministic. > UPDATE command with non-pushdown functions leads to TEIID30253 error > -------------------------------------------------------------------- > > Key: TEIID-4423 > URL: https://issues.jboss.org/browse/TEIID-4423 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.x > Environment: teiid-8.12-Beta1 on Red Hat JBoss Enterprise Application Platform - Version 6.3.0.GA > teiid-9.0.3 on WildFly Full 9.0.2.Final > Reporter: dalex dalex > Assignee: Steven Hawkins > > Running the following queries: > {code:sql} > update test.textagg_test_2 set id =(select uuid());; > {code} > or > {code:sql} > update test.textagg_test_2 set id =(select rand());; > {code} > leads to the following errors: > {code} > TEIID30253 Source UPDATE or DELETE command "UPDATE test.textagg_test_2 SET id = (SELECT uuid() LIMIT 2)" contains non-pushdown constructs and no compensating action can be taken as the table lacks a unique key or the source does not support equality predicates. > {code} > and > {code} > TEIID30253 Source UPDATE or DELETE command "UPDATE test.textagg_test_2 SET id = convert((SELECT rand() LIMIT 2), string)" contains non-pushdown constructs and no compensating action can be taken as the table lacks a unique key or the source does not support equality predicates. > {code} > though the following query: > {code:sql} > update test.textagg_test_2 set id =(select now());; > {code} > works without errors. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 September 2016