April 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-170) Automate materialization to JDG

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-170?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-170: --------------------------------- Sprint: DV Sprint 60, DV Sprint 61, DV Sprint 62 (was: DV Sprint 60, DV Sprint 61) > Automate materialization to JDG > ------------------------------- > > Key: TEIIDSB-170 > URL: https://issues.redhat.com/browse/TEIIDSB-170 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: OpenShift > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > Original Estimate: 1 week > Time Spent: 1 hour > Remaining Estimate: 4 days, 7 hours > > Create an internal materialization replacement needs that is turnkey materialization to JDG (little to no user setup required) > - the operator may create the infinispan cluster if needed > - the status table and internal representation of the materialization target would be setup automatically > For the user this would be as simple marking a view as materialized and then it would be populated in jdg upon deployment. They would not have any concerns with cache naming, status tables, etc. > For simplicity the initial version would make a similar assumption to the current internal logic - it is for only a specific vdb. If the vdb cr is modified, then it's expected that the cache would be recreated. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-186) Fix to use only use alias name from ExternalSource

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-186?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-186: --------------------------------- Sprint: DV Sprint 62 > Fix to use only use alias name from ExternalSource > -------------------------------------------------- > > Key: TEIIDSB-186 > URL: https://issues.redhat.com/browse/TEIIDSB-186 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > > As the code progressed the usage of translator name and alias name from ExternalSource class is interchangeably used. This is leading to confusion in terms of development and documents. > Need to fix all the places where the translator name used to use alias name with Spring Boot engine. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-187) Need to pull out the "property prefix" to ExternalSource

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-187?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-187: --------------------------------- Sprint: DV Sprint 62 > Need to pull out the "property prefix" to ExternalSource > -------------------------------------------------------- > > Key: TEIIDSB-187 > URL: https://issues.redhat.com/browse/TEIIDSB-187 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core > Reporter: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > > The prefix of the source like "org.spring.teiid.data.xxx" kind of property patterns are defined in the ConnectionFactory classes, this needs to be pulled into ExternalSource class, then this can be one central place everything about translator and source is managed. > Consider externalizing ExternalSource information into a "json" configuration file, then this can be then used in Operator code load and enforce dependencies and pom file generation and property generation from a single location. Right now all this looks very hacky as it spread out across projects. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-186) Fix to use only use alias name from ExternalSource

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-186?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-186: --------------------------------- Story Points: 1 > Fix to use only use alias name from ExternalSource > -------------------------------------------------- > > Key: TEIIDSB-186 > URL: https://issues.redhat.com/browse/TEIIDSB-186 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > > As the code progressed the usage of translator name and alias name from ExternalSource class is interchangeably used. This is leading to confusion in terms of development and documents. > Need to fix all the places where the translator name used to use alias name with Spring Boot engine. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5929) NPE in RuleRaiseNull rule when using "insert into" command

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5929?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5929. ----------------------------------- Resolution: Done The assumption in rule raise null with the first branch of a union was that the parent source node / project were related to an inline view, not project into. An additional check was needed. > NPE in RuleRaiseNull rule when using "insert into" command > ---------------------------------------------------------- > > Key: TEIID-5929 > URL: https://issues.redhat.com/browse/TEIID-5929 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 13.1 > Reporter: Dmitrii Pogorelov > Assignee: Steven Hawkins > Priority: Critical > Fix For: 14.0, 13.1.1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > An NPE occurs when running the following query: > {code:sql} > insert into test_dwh_pg.test_mat_simplified select * from views.mat_test_view_simplified ;; > {code} > stacktrace: > {code} > 2020-04-07 12:07:58,375 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue26) tqwiPNv56nHR TEIID30019 Unexpected exception for request tqwiPNv56nHR.10: java.lang.NullPointerException at org.teiid.query.optimizer.relational.rules.RuleRaiseNull.raiseNullNode(RuleRaiseNull.java:174) at org.teiid.query.optimizer.relational.rules.RuleRaiseNull.execute(RuleRaiseNull.java:66) at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:1101) at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:235) at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:181) at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:483) at org.teiid.dqp.internal.process.Request.processRequest(Request.java:511) at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:671) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:350) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:43) at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:284) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:281) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:124) at org.teiid.dqp.internal.process.ThreadReuseExecutor$2.run(ThreadReuseExecutor.java:212) 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.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5929) NPE in RuleRaiseNull rule when using "insert into" command

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5929?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5929: ---------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > NPE in RuleRaiseNull rule when using "insert into" command > ---------------------------------------------------------- > > Key: TEIID-5929 > URL: https://issues.redhat.com/browse/TEIID-5929 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 13.1 > Reporter: Dmitrii Pogorelov > Assignee: Steven Hawkins > Priority: Critical > Fix For: 14.0, 13.1.1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > An NPE occurs when running the following query: > {code:sql} > insert into test_dwh_pg.test_mat_simplified select * from views.mat_test_view_simplified ;; > {code} > stacktrace: > {code} > 2020-04-07 12:07:58,375 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue26) tqwiPNv56nHR TEIID30019 Unexpected exception for request tqwiPNv56nHR.10: java.lang.NullPointerException at org.teiid.query.optimizer.relational.rules.RuleRaiseNull.raiseNullNode(RuleRaiseNull.java:174) at org.teiid.query.optimizer.relational.rules.RuleRaiseNull.execute(RuleRaiseNull.java:66) at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:1101) at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:235) at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:181) at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:483) at org.teiid.dqp.internal.process.Request.processRequest(Request.java:511) at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:671) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:350) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:43) at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:284) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:281) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:124) at org.teiid.dqp.internal.process.ThreadReuseExecutor$2.run(ThreadReuseExecutor.java:212) 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.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5929) NPE in RuleRaiseNull rule when using "insert into" command

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5929?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5929: ---------------------------------- Fix Version/s: 14.0 13.1.1 Story Points: 0.5 Sprint: DV Sprint 62 Priority: Critical (was: Blocker) > NPE in RuleRaiseNull rule when using "insert into" command > ---------------------------------------------------------- > > Key: TEIID-5929 > URL: https://issues.redhat.com/browse/TEIID-5929 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 13.1 > Reporter: Dmitrii Pogorelov > Assignee: Steven Hawkins > Priority: Critical > Fix For: 14.0, 13.1.1 > > > An NPE occurs when running the following query: > {code:sql} > insert into test_dwh_pg.test_mat_simplified select * from views.mat_test_view_simplified ;; > {code} > stacktrace: > {code} > 2020-04-07 12:07:58,375 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue26) tqwiPNv56nHR TEIID30019 Unexpected exception for request tqwiPNv56nHR.10: java.lang.NullPointerException at org.teiid.query.optimizer.relational.rules.RuleRaiseNull.raiseNullNode(RuleRaiseNull.java:174) at org.teiid.query.optimizer.relational.rules.RuleRaiseNull.execute(RuleRaiseNull.java:66) at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:1101) at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:235) at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:181) at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:483) at org.teiid.dqp.internal.process.Request.processRequest(Request.java:511) at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:671) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:350) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:43) at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:284) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:281) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:124) at org.teiid.dqp.internal.process.ThreadReuseExecutor$2.run(ThreadReuseExecutor.java:212) 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.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5930) FULL JOIN missing data when not using LIMIT clause

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5930?page=com.atlassian.jira.plugi... ] Work on TEIID-5930 started by Steven Hawkins. --------------------------------------------- > FULL JOIN missing data when not using LIMIT clause > -------------------------------------------------- > > Key: TEIID-5930 > URL: https://issues.redhat.com/browse/TEIID-5930 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 13.1 > Reporter: Dmitrii Pogorelov > Assignee: Steven Hawkins > Priority: Blocker > > When commenting out/uncommenting limit clause in the query: > {code:sql} > SELECT COUNT(*) > FROM > ( > SELECT > date_value1 > , id > FROM views.view1_m > Limit 1000000000 > ) v1 > full > JOIN > ( > SELECT > date_value2 > , id > FROM views.view2_m > LIMIT 1000000000 > ) v2 > ON > v1.date_value1 = v2.date_value2 > and v1.id = v2.id ;; > {code} > teiid returns different results, for example, when using limits in all subqueries Teiid will return 3652, but when commenting out all limit clauses teiid in turn will return already 0. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5930) FULL JOIN missing data when not using LIMIT clause

by Dmitrii Pogorelov (Jira)

Dmitrii Pogorelov created TEIID-5930: ---------------------------------------- Summary: FULL JOIN missing data when not using LIMIT clause Key: TEIID-5930 URL: https://issues.redhat.com/browse/TEIID-5930 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 13.1 Reporter: Dmitrii Pogorelov Assignee: Steven Hawkins When commenting out/uncommenting limit clause in the query: {code:sql} SELECT COUNT(*) FROM ( SELECT date_value1 , id FROM views.view1_m Limit 1000000000 ) v1 full JOIN ( SELECT date_value2 , id FROM views.view2_m LIMIT 1000000000 ) v2 ON v1.date_value1 = v2.date_value2 and v1.id = v2.id ;; {code} teiid returns different results, for example, when using limits in all subqueries Teiid will return 3652, but when commenting out all limit clauses teiid in turn will return already 0. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5929) NPE in RuleRaiseNull rule when using "insert into" command

by Dmitrii Pogorelov (Jira)

Dmitrii Pogorelov created TEIID-5929: ---------------------------------------- Summary: NPE in RuleRaiseNull rule when using "insert into" command Key: TEIID-5929 URL: https://issues.redhat.com/browse/TEIID-5929 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 13.1 Reporter: Dmitrii Pogorelov Assignee: Steven Hawkins An NPE occurs when running the following query: {code:sql} insert into test_dwh_pg.test_mat_simplified select * from views.mat_test_view_simplified ;; {code} stacktrace: {code} 2020-04-07 12:07:58,375 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue26) tqwiPNv56nHR TEIID30019 Unexpected exception for request tqwiPNv56nHR.10: java.lang.NullPointerException at org.teiid.query.optimizer.relational.rules.RuleRaiseNull.raiseNullNode(RuleRaiseNull.java:174) at org.teiid.query.optimizer.relational.rules.RuleRaiseNull.execute(RuleRaiseNull.java:66) at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:1101) at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:235) at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:181) at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:483) at org.teiid.dqp.internal.process.Request.processRequest(Request.java:511) at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:671) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:350) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:43) at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:284) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:281) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:124) at org.teiid.dqp.internal.process.ThreadReuseExecutor$2.run(ThreadReuseExecutor.java:212) 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.13.8#713008)

5 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2020