February 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-35) Write example to show Keycloak based OData access in OpenShift

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-35?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIIDSB-35. --------------------------------- Assignee: Ramesh Reddy Resolution: Done Keycloak based example of authentication and authorization is added and documented. > Write example to show Keycloak based OData access in OpenShift > -------------------------------------------------------------- > > Key: TEIIDSB-35 > URL: https://issues.jboss.org/browse/TEIIDSB-35 > Project: Teiid Spring Boot > Issue Type: Task > Components: examples, OData, OpenShift > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > > This example should provide detailed instructions to deploy/use existing Keycloak instance in the OpenShift to be used with the Teiid based service. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-35) Write example to show Keycloak based OData access in OpenShift

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-35?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIIDSB-35: -------------------------------- Fix Version/s: 1.0.3 > Write example to show Keycloak based OData access in OpenShift > -------------------------------------------------------------- > > Key: TEIIDSB-35 > URL: https://issues.jboss.org/browse/TEIIDSB-35 > Project: Teiid Spring Boot > Issue Type: Task > Components: examples, OData, OpenShift > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.0.3 > > > This example should provide detailed instructions to deploy/use existing Keycloak instance in the OpenShift to be used with the Teiid based service. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-40) define logging options

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-40?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIIDSB-40: ------------------------------------- Ok, I have not heard other teams working with this either yet. > define logging options > ---------------------- > > Key: TEIIDSB-40 > URL: https://issues.jboss.org/browse/TEIIDSB-40 > Project: Teiid Spring Boot > Issue Type: Sub-task > Components: OpenShift > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.0.3 > > > It looks like the preferred mechanism with spring boot is to use: > https://github.com/logstash/logstash-logback-encoder > This should make it easier for the aggregate container logging to use the container logs. I'll validate this and update the example appropriately - which we could create a parallel to prometheus for the logging stack / kibana. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5636) Planning error. Could not find symbol disiz__1.DischargeTime

by Mark Tawk (Jira)

[ https://issues.jboss.org/browse/TEIID-5636?page=com.atlassian.jira.plugin... ] Mark Tawk updated TEIID-5636: ----------------------------- Attachment: Planning Error 21-02-2019.txt > Planning error. Could not find symbol disiz__1.DischargeTime > ------------------------------------------------------------ > > Key: TEIID-5636 > URL: https://issues.jboss.org/browse/TEIID-5636 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 10.3.4 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Priority: Critical > Fix For: 12.1, 12.0.1, 11.2.3 > > Attachments: Planning Error 21-02-2019.txt, planning_error.txt > > > Hi, > We're running into this exception. It happens when adding "LEFT OUTER JOIN izisprod.P_DischargeData". I unfortunitaly have no smaller example. We use this table all the time without any previous errors. > 2019-01-31 15:32:36,438 ERROR [org.teiid.PROCESSOR] (Worker172_QueryProcessorQueue57002) JesgvCmnKfP5 TEIID30019 Unexpected exception for request JesgvCmnKfP5.187: org.teiid.core.TeiidRuntimeException: Planning error. Could not find symbol: disiz__1.DischargeTime > at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:363) > at org.teiid.query.processor.relational.JoinNode.initialize(JoinNode.java:129) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:92) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:98) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:98) > at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:87) > at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:223) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:135) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:111) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:160) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:142) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:480) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:350) > 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:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5636) Planning error. Could not find symbol disiz__1.DischargeTime

by Mark Tawk (Jira)

[ https://issues.jboss.org/browse/TEIID-5636?page=com.atlassian.jira.plugin... ] Mark Tawk commented on TEIID-5636: ---------------------------------- The fix has solved the issue of the query we sent. But we are still reproducing the planning error with another query. You find attached the stack trace + query sql + plan [^Planning Error 21-02-2019.txt] > Planning error. Could not find symbol disiz__1.DischargeTime > ------------------------------------------------------------ > > Key: TEIID-5636 > URL: https://issues.jboss.org/browse/TEIID-5636 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 10.3.4 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Priority: Critical > Fix For: 12.1, 12.0.1, 11.2.3 > > Attachments: Planning Error 21-02-2019.txt, planning_error.txt > > > Hi, > We're running into this exception. It happens when adding "LEFT OUTER JOIN izisprod.P_DischargeData". I unfortunitaly have no smaller example. We use this table all the time without any previous errors. > 2019-01-31 15:32:36,438 ERROR [org.teiid.PROCESSOR] (Worker172_QueryProcessorQueue57002) JesgvCmnKfP5 TEIID30019 Unexpected exception for request JesgvCmnKfP5.187: org.teiid.core.TeiidRuntimeException: Planning error. Could not find symbol: disiz__1.DischargeTime > at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:363) > at org.teiid.query.processor.relational.JoinNode.initialize(JoinNode.java:129) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:92) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:98) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:98) > at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:87) > at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:223) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:135) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:111) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:160) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:142) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:480) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:350) > 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:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5644) materialization procedures can hit max string length

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5644?page=com.atlassian.jira.plugin... ] Work on TEIID-5644 started by Steven Hawkins. --------------------------------------------- > materialization procedures can hit max string length > ---------------------------------------------------- > > Key: TEIID-5644 > URL: https://issues.jboss.org/browse/TEIID-5644 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > The concatenations performed to build dynamic sql can become too long for just a string - and by our current rules will be truncated rather than converted to a clob. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5641) Wrong Log Context in SYSADMIN.sql

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5641?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5641. ----------------------------------- Fix Version/s: 12.0.1 Resolution: Done Update the sysadmin ddl to have the proper context. > Wrong Log Context in SYSADMIN.sql > --------------------------------- > > Key: TEIID-5641 > URL: https://issues.jboss.org/browse/TEIID-5641 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1, 12.0.1 > > > Some log contexts used in SYSADMIN.sql are not valid (org.teiid.MATVIEWS) or it should be org.teiid.PROCESSOR.MATVIEWS > for example: > _EXECUTE logMsg(context=>'org.teiid.MATVIEWS', level=>'WARN', msg=>e.exception);_ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5641) Wrong Log Context in SYSADMIN.sql

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5641?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5641: ---------------------------------- Component/s: Query Engine > Wrong Log Context in SYSADMIN.sql > --------------------------------- > > Key: TEIID-5641 > URL: https://issues.jboss.org/browse/TEIID-5641 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1, 12.0.1 > > > Some log contexts used in SYSADMIN.sql are not valid (org.teiid.MATVIEWS) or it should be org.teiid.PROCESSOR.MATVIEWS > for example: > _EXECUTE logMsg(context=>'org.teiid.MATVIEWS', level=>'WARN', msg=>e.exception);_ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5662) Add option to Migration Utility to write to file

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5662?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5662: ------------------------------------ Yes, to make it runable from the root pom. > Add option to Migration Utility to write to file > ------------------------------------------------ > > Key: TEIID-5662 > URL: https://issues.jboss.org/browse/TEIID-5662 > Project: Teiid > Issue Type: Feature Request > Components: Quick Starts, Tooling > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > Fix For: 12.1 > > > Add an option to the Migration Utility for writing the converted vdb to a file, which could include the path to persist it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5641) Wrong Log Context in SYSADMIN.sql

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5641?page=com.atlassian.jira.plugin... ] Work on TEIID-5641 started by Steven Hawkins. --------------------------------------------- > Wrong Log Context in SYSADMIN.sql > --------------------------------- > > Key: TEIID-5641 > URL: https://issues.jboss.org/browse/TEIID-5641 > Project: Teiid > Issue Type: Bug > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Some log contexts used in SYSADMIN.sql are not valid (org.teiid.MATVIEWS) or it should be org.teiid.PROCESSOR.MATVIEWS > for example: > _EXECUTE logMsg(context=>'org.teiid.MATVIEWS', level=>'WARN', msg=>e.exception);_ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2019