October 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3778) Mark hbase/phoenix as supporting limit

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3778?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3778. ----------------------------------- Fix Version/s: 8.13 Resolution: Done Added the supports method. > Mark hbase/phoenix as supporting limit > -------------------------------------- > > Key: TEIID-3778 > URL: https://issues.jboss.org/browse/TEIID-3778 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.11 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12.1, 8.13 > > > The support for row limit should be added. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3764) HBase - Phoenix driver does not support UNION

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3764?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3764. ----------------------------------- Resolution: Done Addressed with an hbase specific workaround to convert the union into a select distinct against an inline view. This could be promoted to the engine if there are other translators that need a similar fix (although there are currently none that I'm aware of). > HBase - Phoenix driver does not support UNION > --------------------------------------------- > > Key: TEIID-3764 > URL: https://issues.jboss.org/browse/TEIID-3764 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12.1, 8.13 > > > Phoenix JDBC driver does not support UNION statement, only UNION ALL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3764) HBase - Phoenix driver does not support UNION

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3764?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3764: ---------------------------------- Component/s: Misc. Connectors Fix Version/s: 8.12.1 8.13 > HBase - Phoenix driver does not support UNION > --------------------------------------------- > > Key: TEIID-3764 > URL: https://issues.jboss.org/browse/TEIID-3764 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12.1, 8.13 > > > Phoenix JDBC driver does not support UNION statement, only UNION ALL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3763) WS connector oauth security setting not work in Embedded

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3763?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3763: ------------------------------------- Issue Type: Bug (was: Feature Request) Fix Version/s: 8.12.x (was: 8.13) Summary: WS connector oauth security setting not work in Embedded (was: WS connector security setting not work in Embedded) Affects Version/s: 8.12 (was: 8.13) Assignee: (was: Steven Hawkins) We'll could at least address the NPE, but as Ramesh says the usage of the this resource adapter for oauth may depend upon usage in a JEE container. > WS connector oauth security setting not work in Embedded > -------------------------------------------------------- > > Key: TEIID-3763 > URL: https://issues.jboss.org/browse/TEIID-3763 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12 > Reporter: Kylin Soong > Fix For: 8.12.x > > > In WSConnectionImpl setDispatchProperties setting depend on Security Subject: > {code} > else if (this.mcf.getAsSecurityType() == WSManagedConnectionFactory.SecurityType.OAuth) { > Subject subject = ConnectionContext.getSubject(); > if (subject != null) { > } > ... > } > {code} > Note if run WS connector with security in Embedded, ConnectionContext.getSubject() return null, the cause exception throw. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[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 updated TEIID-3759: ---------------------------------- Fix Version/s: 8.12.x > 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: Enhancement > Components: Embedded, OData > Affects Versions: 8.12 > Reporter: Gary Gregory > Assignee: Ramesh Reddy > Fix For: 8.12.x > > > 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)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3765) HBase - Phoenix does not support scalar subquery

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3765?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3765: ---------------------------------- Component/s: Misc. Connectors Description: Phoenix driver does not support a scalar subquery in a SELECT - E.g. SELECT a, (SELECT...) ... (was: Phoenix driver does not support nested SELECT statement. E.g. SELECT a, (SELECT...) ...) Fix Version/s: 8.12.1 8.13 Summary: HBase - Phoenix does not support scalar subquery (was: HBase - Phoenix does not support nested select) > HBase - Phoenix does not support scalar subquery > ------------------------------------------------ > > Key: TEIID-3765 > URL: https://issues.jboss.org/browse/TEIID-3765 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12.1, 8.13 > > > Phoenix driver does not support a scalar subquery in a SELECT - E.g. SELECT a, (SELECT...) ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 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 resolved TEIID-3777. ----------------------------------- Resolution: Done Add a similar validation as postgresql to prevent order bys on aggregates with distinct to reference values other than the aggregate parameters. And updated the initialization logic to consider the ordering first. Thanks for catching this. > 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)

9 years, 3 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 updated TEIID-3777: ---------------------------------- Component/s: Query Engine Fix Version/s: 8.11.5 8.12.1 8.13 The aggregate initialization logic is first looking at the distinct flag - and ignoring the order by. > 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 > 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)

9 years, 3 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 updated TEIID-3777: ---------------------------------- Priority: Critical (was: Major) > 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)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3763) WS connector security setting not work in Embedded

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3763?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3763: ------------------------------------- The "Subject" is set in higher order of calling thread's context, thus Managed Connection receives it. Setting them directly on Managed Connection is not correct for pass-through scenarios. The resource adapters are designed for JEE environments, especially for JBoss EAP. When resource-adapter connections are selected for execution, the thread context happens through JEE mechanics. That said, usage of them directly in "Embedded" as is not appropriate as is in all situations. We need to think, if/how we need to package/utilize differently in embedded scenario. > WS connector security setting not work in Embedded > -------------------------------------------------- > > Key: TEIID-3763 > URL: https://issues.jboss.org/browse/TEIID-3763 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.13 > Reporter: Kylin Soong > Assignee: Steven Hawkins > Fix For: 8.13 > > > In WSConnectionImpl setDispatchProperties setting depend on Security Subject: > {code} > else if (this.mcf.getAsSecurityType() == WSManagedConnectionFactory.SecurityType.OAuth) { > Subject subject = ConnectionContext.getSubject(); > if (subject != null) { > } > ... > } > {code} > Note if run WS connector with security in Embedded, ConnectionContext.getSubject() return null, the cause exception throw. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2015