January 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3759) Missing Apache Olingo dependency in Teiid 8.12.0.Final

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3759?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3759. --------------------------------- > Missing Apache Olingo dependency in Teiid 8.12.0.Final > ------------------------------------------------------ > > Key: TEIID-3759 > URL: https://issues.jboss.org/browse/TEIID-3759 > Project: Teiid > Issue Type: Quality Risk > Components: Embedded, OData > Affects Versions: 8.12 > Reporter: Gary Gregory > Assignee: Ramesh Reddy > Fix For: 8.12.1 > > > I think Teiid might have a missing Apache Olingo dependency: > {noformat} > java.lang.NoClassDefFoundError: org/apache/olingo/commons/api/edm/provider/CsdlBindingTarget > at org.teiid.translator.odata4.ODataExecutionFactory.getMetadataProcessor(ODataExecutionFactory.java:140) > at org.teiid.deployers.TranslatorUtil.buildTranslatorProperties(TranslatorUtil.java:280) > at org.teiid.deployers.TranslatorUtil.buildTranslatorMetadata(TranslatorUtil.java:252) > ... > Caused by: java.lang.ClassNotFoundException: org.apache.olingo.commons.api.edm.provider.CsdlBindingTarget > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > ... 35 more > {noformat} > There is no Apache Olingo in {{optional/odata}} or {{lib/optional/odata4}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3743) Multiple Count Distinct Columns Fails for Impala

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3743?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3743. --------------------------------- > Multiple Count Distinct Columns Fails for Impala > ------------------------------------------------ > > Key: TEIID-3743 > URL: https://issues.jboss.org/browse/TEIID-3743 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.11.4 > Reporter: Scott Wallace > Assignee: Steven Hawkins > Fix For: 8.12 > > > Teiid Impala translator incorrectly allows multiple count distinct columns, which fails to execute since it is not supported by Impala. > Per Cloudera documentation: > {quote}By default, Impala only allows a single COUNT(DISTINCT columns) expression in each query. > To produce the same result as multiple COUNT(DISTINCT) expressions, you can use the following technique for queries involving a single table: > select v1.c1 result1, v2.c1 result2 from (select count(distinct col1) as c1 from t1) v1 cross join (select count(distinct col2) as c1 from t1) v2;{quote} > The Teiid-Impala translator should ideally rewrite the query as necessary so that the query does not fail executing multiple count distincts against Impala. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3781) Queries are not killed even if the client sends a cancel request

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3781?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3781. --------------------------------- > Queries are not killed even if the client sends a cancel request > ---------------------------------------------------------------- > > Key: TEIID-3781 > URL: https://issues.jboss.org/browse/TEIID-3781 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 7.0 > Reporter: Salvatore R > Assignee: Steven Hawkins > Fix For: 8.12.1, 8.13 > > > I have different behaviors when I try to cancel the following queries: > {code:sql} > SELECT COUNT(*) > FROM > (SELECT * FROM my.address) as x1, > (SELECT * FROM my.address) as y1 > {code} > and > {code:sql} > SELECT COUNT(*) > FROM > (SELECT * FROM my.address limit 10000) as x1, > (SELECT * FROM my.address limit 10000) as y1 > {code} > where "my.address" is a table with around 20000 rows in MySQL. > The first query is immediately cancelled but the second one continues to run until the end and it is never killed. > Looking at the generated plans, the main difference is that the first query is fully pushed down to MySQL while the second one is not. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3777) ORDER BY DESC is ignored in STRING_AGG function when DISTINCT is also specified

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3777?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3777. --------------------------------- > ORDER BY DESC is ignored in STRING_AGG function when DISTINCT is also specified > ------------------------------------------------------------------------------- > > Key: TEIID-3777 > URL: https://issues.jboss.org/browse/TEIID-3777 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Salvatore R > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.11.5, 8.12.1, 8.13 > > > When both DISTINCT and ORDER BY clause are specified in a STRING_AGG function, the result of the aggregate function is not correctly sorted. > For example, running the following query: > {code:sql} > select > string_agg(col1, ',' ORDER BY col1 DESC) as orderByDesc, > string_agg(col1, ',' ORDER BY col1 ASC) as orderByAsc, > string_agg(DISTINCT col1, ',' ORDER BY col1 DESC) as distinctOrderByDesc, > string_agg(DISTINCT col1, ',' ORDER BY col1 ASC) as distinctOrderByAsc > from ( > SELECT 'b' as col1 > UNION ALL > SELECT 'c' as col1 > UNION ALL > SELECT 'a' as col1 > UNION ALL > SELECT 'c' as col1 > ) x > {code} > the result is: > ||orderByDesc||orderByAsc||distinctOrderByDesc||distinctOrderByAsc|| > |c,c,b,a|a,b,c,c|a,b,c|a,b,c| -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3762) OData V2: $value on property is not supported

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3762?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3762. --------------------------------- > OData V2: $value on property is not supported > --------------------------------------------- > > Key: TEIID-3762 > URL: https://issues.jboss.org/browse/TEIID-3762 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.12.1, 8.13 > > > A raw property value can be retrieved using the $value segment, like > {code} > http://localhost:8080/odata/vdb/table/property/$value > {code} > This should be suported, or should throw a proper error -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3736) Allow date formatted string literals to be parsed as timestamps

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3736?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3736. --------------------------------- > Allow date formatted string literals to be parsed as timestamps > --------------------------------------------------------------- > > Key: TEIID-3736 > URL: https://issues.jboss.org/browse/TEIID-3736 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > For consistency with most major vendors we should support allowing date literals to be parsed as timestamps. For example: > timestamp_col > '2001-01-01' > which would prevent the predicate from being resolved as a string comparison. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3756) Order By clause specified in STRING_AGG function is skipped when pushed down to PostgreSQL

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3756?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3756. --------------------------------- > Order By clause specified in STRING_AGG function is skipped when pushed down to PostgreSQL > ------------------------------------------------------------------------------------------ > > Key: TEIID-3756 > URL: https://issues.jboss.org/browse/TEIID-3756 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Salvatore R > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.5 > > > I defined a small table in PostgreSQL as follows: > {code:sql} > create table test_string_agg (col1 varchar(10)) > insert into test_string_agg VALUES ('b'); > insert into test_string_agg VALUES ('a'); > insert into test_string_agg VALUES ('c'); > {code} > When I run a query with a STRING_AGG function where an ORDER BY clause is specified, the strings are not concatenated in the expected order. For example, these three queries: > {code:sql} > select string_agg(col1, ' , ' order by col1) from pg.test_string_agg; > select string_agg(col1, ' , ' order by col1 desc) from pg.test_string_agg; > select string_agg(col1, ' , ' order by col1 asc) from pg.test_string_agg; > {code} > return all the same result "b , a , c". > It seems that the ORDER BY clause is not pushed down to PostgreSQL, in fact all the three rewritten queries executed in PostgreSQL look like: > {code:sql} > SELECT STRING_AGG(g_0."col1", ' , ') FROM "public"."test_string_agg" AS g_0 > {code} > If the STRING_AGG function is not pushed down (e.g. in MySQL), I get an expected result. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3761) OData V2: The property based response and Function based responses are incorrect per specification

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3761?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3761. --------------------------------- > OData V2: The property based response and Function based responses are incorrect per specification > -------------------------------------------------------------------------------------------------- > > Key: TEIID-3761 > URL: https://issues.jboss.org/browse/TEIID-3761 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.12.1, 8.13 > > > The property request like > {code} > http://localhost:8080/odata/vdb/table/property > http://localhost:8080/odata/vdb/table/property/$value > {code} > needs to return a property based response, instead they are returning the "entity" based response. > The function with simple scalar return, should return just simple data > {code} > http://localhost:8080/odata/vdb/func?param=value > {code} > instead it returning the collection based data -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3039?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3039. --------------------------------- > OData V2: 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 > Assignee: Ramesh Reddy > Fix For: 8.12.1, 8.13 > > > 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.4.11#64026)

8 years, 4 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3039?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3039: ---------------------------------- Fix Version/s: 8.13 > OData V2: 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 > Assignee: Ramesh Reddy > Fix For: 8.12.1, 8.13 > > > 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.4.11#64026)

8 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2016