March 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-62) OpenApi 3.0 Support for OData

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-62: ----------------------------------- Summary: OpenApi 3.0 Support for OData Key: TEIIDSB-62 URL: https://issues.jboss.org/browse/TEIIDSB-62 Project: Teiid Spring Boot Issue Type: Feature Request Reporter: Ramesh Reddy Support OpenAPI 3.0 document generation with OData service -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5702) Support Keycloak based OAuth authentication for OData Through 3scale

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5702: ----------------------------------- Summary: Support Keycloak based OAuth authentication for OData Through 3scale Key: TEIID-5702 URL: https://issues.jboss.org/browse/TEIID-5702 Project: Teiid Issue Type: Enhancement Reporter: Ramesh Reddy Assignee: Steven Hawkins Support the authentication for OData through 3scale -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5682) Raise aggregation to allow for join pushdown

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5682?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5682: --------------------------------------- This seems a little involved for the problem that it is solving. With an incoming query such as: SELECT g0.e1, g0.e2, g0.e3, /*+ MJ */ (SELECT ARRAY_AGG((g1.e1, g1.e2) ORDER BY g1.e1) FROM PM1.G2 AS g1 WHERE g0.e2 = g1.e2) FROM PM1.G1 AS g0 ORDER BY g0.e2 SELECT g0.e1, g0.e2, g0.e3, X__1.expr1 AS expr4 FROM PM1.G1 AS g0 LEFT OUTER JOIN (SELECT ARRAY_AGG((g1.e1, g1.e2) ORDER BY g1.e1) AS expr1, g1.e2 FROM PM1.G2 AS g1 GROUP BY g1.e2) AS X__1 ON g0.e2 = X__1.e2 ORDER BY g0.e2 We need to get to: SELECT g0.e1, g0.e2, g0.e3, ARRAY_AGG((X__1.e1, X__1.e2) ORDER BY X__1.e1) ) FILTER (WHERE X__1.e1 IS NOT NULL) AS expr4 FROM PM1.G1 AS g0 LEFT OUTER JOIN (SELECT g1.e1, g1.e2 FROM PM1.G2 AS g1) AS X__1 ON g0.e2 = X__1.e2 GROUP BY g0.e1, g0.e2, g0.e3 ORDER BY g0.e2 Note that all projected g0 columns must be sortable - this is not always the case. It also requires attaching a filter to aggregates that can be null dependent when there is an outer join. And finally it can't have any intervening usage of aggregate values or even complex projection between the logical subquery grouping root and it join parent - this will generally be the case for expand, but can't generally be assumed. A simpler approach would either be to either already aggregate the other top level columns: select g0.e2, array_agg(g0.e1 ...) Or not use the nested aggregation and process the expand like the older style - but that only makes sense for a single expand. > Raise aggregation to allow for join pushdown > -------------------------------------------- > > Key: TEIID-5682 > URL: https://issues.jboss.org/browse/TEIID-5682 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > In some plans, for example those created by odata expand see TEIID-5680, the resulting query has the form of: > select tbl1-cols from tbl1 left outer join (select cols, aggregates ... from tbl2 group by cols) on (some non-aggregate predicate) > If the aggregates or other intervening constructs are not able to be pushed the result will be a federated join. > In most instances (where the tbl1 columns are sortable) it's possible to change this to: > select tbl1-cols aggregates from tbl1 left outer join tbl1 on (...) group by tbl1-cols, cols > which can allow the pushdown of the join to proceed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5406) Allow usage of long datatype as the increment parameter in TimestampAdd function

by Dmitrii Pogorelov (Jira)

[ https://issues.jboss.org/browse/TEIID-5406?page=com.atlassian.jira.plugin... ] Dmitrii Pogorelov commented on TEIID-5406: ------------------------------------------ Hi [~shawkins], the issue was resolved previous year but just a question: do I understand correctly that some of DB still can treat the fractional second parameter as Integer type? That's why you added the check on Integer range? > Allow usage of long datatype as the increment parameter in TimestampAdd function > -------------------------------------------------------------------------------- > > Key: TEIID-5406 > URL: https://issues.jboss.org/browse/TEIID-5406 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 10.2 > Environment: teiid-10.2.0 on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) > Reporter: Dmitrii Pogorelov > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.1 > > > Currently the TIMESTAMPADD(interval, count, timestamp) expects the count parameter to be integer. This is inconsistent with the return value of the TIMSTAMPDIFF function that is long. Thus we cannot take the fraction of the count returned by TIMSTAMPDIFF and submit it to TIMESTAMPADD. Since the SQL_TSI_FRAC_SECOND difference is too large for most human values (and it's the only way to retrieve millis, even though millions of millis), we need a way to submit this data to TIMSTAMPADD. > 1. There is an inconsistency when adding 1 billion fractions of a second. Please execute the script below, one adds one billion minus one, the next one exactly 1bln fractions which results in two values, one of which is 1 fraction larger than expected: > {code:sql} > Select TimestampAdd(SQL_TSI_FRAC_SECOND, 999999999, Cast(CurDate() as timestamp)) > Union All > Select TimestampAdd(SQL_TSI_FRAC_SECOND, 999999999 + 1, Cast(CurDate() as timestamp));; > {code} > 2. Another example: > {code:sql} > Begin > Declare timestamp initialDate = CurDate(); > Declare long diff = TimestampDiff(SQL_TSI_FRAC_SECOND, initialDate, TimestampAdd(SQL_TSI_DAY, 1, initialDate)); > Declare timestamp back = TimestampAdd(SQL_TSI_FRAC_SECOND, diff, initialDate); > select initialDate, back; > End ;; > {code} > which leads to the following error message: > {code:noformat} > 2018-07-03 10:10:33,942 WARN [org.teiid.PROCESSOR] (Worker7_QueryProcessorQueue47) 1RBg/ooz5vx7 TEIID30020 Processing exception for request 1RBg/ooz5vx7.27 'TEIID30070 The function > 'TimestampAdd(SQL_TSI_FRAC_SECOND, VARIABLES.diff, VARIABLES.initialDate)' is a valid function form, but the arguments do not match a known type signature and cannot be converted usi > ng implicit type conversions.'. Originally QueryResolverException ResolverVisitor.java:757.: org.teiid.api.exception.query.QueryResolverException: TEIID30070 The function 'TimestampA > dd(SQL_TSI_FRAC_SECOND, VARIABLES.diff, VARIABLES.initialDate)' is a valid function form, but the arguments do not match a known type signature and cannot be converted using implicit > type conversions. > at org.teiid.query.resolver.util.ResolverVisitor.resolveFunction(ResolverVisitor.java:757) > at org.teiid.query.resolver.util.ResolverVisitor.visit(ResolverVisitor.java:392) > at org.teiid.query.sql.symbol.Function.acceptVisitor(Function.java:169) > at org.teiid.query.sql.navigator.AbstractNavigator.visitVisitor(AbstractNavigator.java:50) > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.postVisitVisitor(PreOrPostOrderNavigator.java:57) > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:194) > at org.teiid.query.sql.symbol.Function.acceptVisitor(Function.java:169) > at org.teiid.query.resolver.util.ResolverVisitor.resolveLanguageObject(ResolverVisitor.java:1456) > at org.teiid.query.resolver.command.UpdateProcedureResolver.resolveStatement(UpdateProcedureResolver.java:234) > at org.teiid.query.resolver.command.UpdateProcedureResolver.resolveBlock(UpdateProcedureResolver.java:127) > at org.teiid.query.resolver.command.UpdateProcedureResolver.resolveCommand(UpdateProcedureResolver.java:110) > at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:282) > at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:128) > at org.teiid.dqp.internal.process.Request.resolveCommand(Request.java:282) > at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:418) > at org.teiid.dqp.internal.process.Request.processRequest(Request.java:486) > at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:660) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:339) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:47) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:276) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:277) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:115) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:206) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5701) Add settings.xml to the openshfit-examples

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5701?page=com.atlassian.jira.plugin... ] Van Halbert resolved TEIID-5701. -------------------------------- Resolution: Done > Add settings.xml to the openshfit-examples > ------------------------------------------ > > Key: TEIID-5701 > URL: https://issues.jboss.org/browse/TEIID-5701 > Project: Teiid > Issue Type: Task > Components: Build/Kits, Quick Starts > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > With DV being released in tech-preview and the artifacts will be released in the earlyaccess MRRC repo, there needs to be a settings.xml file that has the MRRC earlyaccess and ga repos configured. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5682) Raise aggregation to allow for join pushdown

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5682?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5682: --------------------------------------- With cardinalities set this issue is somewhat mitigated as the join will be planned as a dependent join. The rationale for raising the aggregation is if the cardinalties aren't set and the join can be pushed. The grouping and order by operations can then be combined. > Raise aggregation to allow for join pushdown > -------------------------------------------- > > Key: TEIID-5682 > URL: https://issues.jboss.org/browse/TEIID-5682 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > In some plans, for example those created by odata expand see TEIID-5680, the resulting query has the form of: > select tbl1-cols from tbl1 left outer join (select cols, aggregates ... from tbl2 group by cols) on (some non-aggregate predicate) > If the aggregates or other intervening constructs are not able to be pushed the result will be a federated join. > In most instances (where the tbl1 columns are sortable) it's possible to change this to: > select tbl1-cols aggregates from tbl1 left outer join tbl1 on (...) group by tbl1-cols, cols > which can allow the pushdown of the join to proceed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5682) Raise aggregation to allow for join pushdown

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5682?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5682: ---------------------------------- Fix Version/s: 12.2 (was: 12.x) > Raise aggregation to allow for join pushdown > -------------------------------------------- > > Key: TEIID-5682 > URL: https://issues.jboss.org/browse/TEIID-5682 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > In some plans, for example those created by odata expand see TEIID-5680, the resulting query has the form of: > select tbl1-cols from tbl1 left outer join (select cols, aggregates ... from tbl2 group by cols) on (some non-aggregate predicate) > If the aggregates or other intervening constructs are not able to be pushed the result will be a federated join. > In most instances (where the tbl1 columns are sortable) it's possible to change this to: > select tbl1-cols aggregates from tbl1 left outer join tbl1 on (...) group by tbl1-cols, cols > which can allow the pushdown of the join to proceed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5682) Raise aggregation to allow for join pushdown

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5682?page=com.atlassian.jira.plugin... ] Work on TEIID-5682 started by Steven Hawkins. --------------------------------------------- > Raise aggregation to allow for join pushdown > -------------------------------------------- > > Key: TEIID-5682 > URL: https://issues.jboss.org/browse/TEIID-5682 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.x > > > In some plans, for example those created by odata expand see TEIID-5680, the resulting query has the form of: > select tbl1-cols from tbl1 left outer join (select cols, aggregates ... from tbl2 group by cols) on (some non-aggregate predicate) > If the aggregates or other intervening constructs are not able to be pushed the result will be a federated join. > In most instances (where the tbl1 columns are sortable) it's possible to change this to: > select tbl1-cols aggregates from tbl1 left outer join tbl1 on (...) group by tbl1-cols, cols > which can allow the pushdown of the join to proceed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5701) Add settings.xml to the openshfit-examples

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5701?page=com.atlassian.jira.plugin... ] Work on TEIID-5701 stopped by Van Halbert. ------------------------------------------ > Add settings.xml to the openshfit-examples > ------------------------------------------ > > Key: TEIID-5701 > URL: https://issues.jboss.org/browse/TEIID-5701 > Project: Teiid > Issue Type: Task > Components: Build/Kits, Quick Starts > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > With DV being released in tech-preview and the artifacts will be released in the earlyaccess MRRC repo, there needs to be a settings.xml file that has the MRRC earlyaccess and ga repos configured. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5701) Add settings.xml to the openshfit-examples

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5701?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5701: ------------------------------------ Updating README's so that the mvn commands include overriding the settings.xml > Add settings.xml to the openshfit-examples > ------------------------------------------ > > Key: TEIID-5701 > URL: https://issues.jboss.org/browse/TEIID-5701 > Project: Teiid > Issue Type: Task > Components: Build/Kits, Quick Starts > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > With DV being released in tech-preview and the artifacts will be released in the earlyaccess MRRC repo, there needs to be a settings.xml file that has the MRRC earlyaccess and ga repos configured. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2019