October 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-134) OData 2 source fails with default headers

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-134: -------------------------------------- Summary: OData 2 source fails with default headers Key: TEIIDSB-134 URL: https://issues.jboss.org/browse/TEIIDSB-134 Project: Teiid Spring Boot Issue Type: Bug Components: core, OData Reporter: Steven Hawkins Fix For: 1.3.0 The translator sets the content type by default: https://github.com/teiid/teiid/blob/06b9828a3fd6dafa358ff93f0a4803e69a3bf... This seems to be handled differently by CXF and spring webservice sources. A user is reporting that a simple request (without a payload) succeeds with CXF, but fails with spring. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5740) Create tables/procedures for query plans and vdb info

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5740?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5740: --------------------------------------- It looks like the best option is to emulate pg - at least in terms of the sql EXPLAIN ANALYZE with some of the options supported. We of course will return a different plan document, but in some very basic scenarios there will be support. I was also considering if adding some kind of plan information through odata makes any scene, but I don't see that it does at this point. There's no high level concept of an odata plan. For the majority of simple reads there is a direct correspondence of odata query to a sql query, but in many instances multiple queries get issued and we have no good way of tying that information together. On the vdb information we can continue to expand the VIRTUALDATABASE system table for well known properties, but will need to introduce a vdbproperties table or assign some identifier to the vdb itself and reuse the properties table. We'll also want to mimic information_schema representations of grant/role information, but that may need to be spawned as a separate issue. > Create tables/procedures for query plans and vdb info > ----------------------------------------------------- > > Key: TEIID-5740 > URL: https://issues.jboss.org/browse/TEIID-5740 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > We need another mechanism for viewing plans - either a procedure or a table. We also have a lot of vdb information that is not exposed via system metadata. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-133) Add "jdbc-simple" and "jdbc-ansi" translators

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-133: ------------------------------------ Summary: Add "jdbc-simple" and "jdbc-ansi" translators Key: TEIIDSB-133 URL: https://issues.jboss.org/browse/TEIIDSB-133 Project: Teiid Spring Boot Issue Type: Feature Request Components: core Reporter: Ramesh Reddy Fix For: 1.3.0 Add support for the "jdbc-simple" and "jdbc-ansi" translators. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5833) Update extension metadata uri's

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5833?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5833. ----------------------------------- Resolution: Done Given that designer and it's associated extension mechanism have gone away the decision was to just remove the notion of SET NAMESPACE - but there are a few concessions for backwards compatibility. Most users will not be affected by this change. At worst if someone introduced a custom namespace, then they need to change their java code and their ddl/sql - but the changes are straight-forward. The docs have been update, and we can expand as needed. > Update extension metadata uri's > ------------------------------- > > Key: TEIID-5833 > URL: https://issues.jboss.org/browse/TEIID-5833 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > There are a lot of long/old extension metadata uris - including the odata one which still references teiid designer. We should see about making these simpler - perhaps even dropping the notion of fqn vs prefix altogether so that we just deal with the raw prefixes. > The only issue with changes is when the extension properties are left fully qualified in the metadata. We'd need to lookup under both the old and new versions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5834) Class cast exception using web service with bind varables

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5834?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5834. ----------------------------------- Fix Version/s: 13.0 12.3.1 Resolution: Done The issue is that when the IN predicate needs split (the ws translator only handles equality) and there's a dependent join predicate on the same independent symbol, then the class cast is happening. The logic needed a small adjustment. > Class cast exception using web service with bind varables > --------------------------------------------------------- > > Key: TEIID-5834 > URL: https://issues.jboss.org/browse/TEIID-5834 > Project: Teiid > Issue Type: Bug > Affects Versions: 11.1.2 > Reporter: Mike Higgins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0, 12.3.1 > > > I am using a restful web service, which works fine if literal values are used to constrain it. However, when I use bind variables, it gives me a traceback: > java.lang.ClassCastException: org.teiid.query.sql.lang.ImmutableCompareCriteria cannot be cast to org.teiid.query.sql.lang.AbstractSetCriteria > at org.teiid.query.processor.relational.DependentCriteriaProcessor.prepareCriteria(DependentCriteriaProcessor.java:352) > at org.teiid.query.processor.relational.DependentProcedureCriteriaProcessor.prepareNextCommand(DependentProcedureCriteriaProcessor.java:60) > at org.teiid.query.processor.relational.DependentProcedureExecutionNode.prepareNextCommand(DependentProcedureExecutionNode.java:88) > at org.teiid.query.processor.relational.PlanExecutionNode.open(PlanExecutionNode.java:79) > at org.teiid.query.processor.relational.DependentProcedureExecutionNode.open(DependentProcedureExecutionNode.java:108) > at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) > at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) > at org.teiid.query.processor.relational.JoinStrategy.openRight(JoinStrategy.java:101) > at org.teiid.query.processor.relational.JoinNode.nextBatchDirectInternal(JoinNode.java:256) > at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:200) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) > at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:141) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:148) > 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:492) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:362) > ... 8 more > The SQL is: > SELECT CAIMANM.LM_BIOLOGICAL_SYSTEM."BIOLOGICAL_SYSTEM_UID", > WS_CLUSTER.WS_CLUSTER_T."VH_SPECIES", > WS_CLUSTER.WS_CLUSTER_T."PROJECT_SHORT_NAME", > WS_CLUSTER.WS_CLUSTER_T."biosysid" > FROM caimanm.lm_biological_system > LEFT OUTER JOIN WS_cluster.WS_cluster_t > ON (CAIMANM.LM_BIOLOGICAL_SYSTEM."BIOLOGICAL_SYSTEM_UID" = WS_CLUSTER.WS_CLUSTER_T."biosysid") > AND (WS_CLUSTER.WS_CLUSTER_T."biosysid" in (?, ?, ?)) > WHERE (CAIMANM.LM_BIOLOGICAL_SYSTEM."BIOLOGICAL_SYSTEM_UID" in (?, ?, ?)) > Where WS_CLUSTER is the web service. I didn't find any issues about this so I was not sure if a later version would work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5492) Upgrade to Infinispan 9.4

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5492?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-5492: ----------------------------------- Assignee: Ramesh Reddy > Upgrade to Infinispan 9.4 > ------------------------- > > Key: TEIID-5492 > URL: https://issues.jboss.org/browse/TEIID-5492 > Project: Teiid > Issue Type: Task > Components: JDG Connector > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 13.0 > > > To address at least one outstanding issue we need to further upgrade to 9.4. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-127) "No registered data sources found" if used "management.server.port=8081"

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-127?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIIDSB-127. ---------------------------------- Resolution: Done Used BeanDefinition Interceptor at the start to define the dependecies on "dataSource" to avoid the issue of early initialization. > "No registered data sources found" if used "management.server.port=8081" > ------------------------------------------------------------------------ > > Key: TEIIDSB-127 > URL: https://issues.jboss.org/browse/TEIIDSB-127 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource > Affects Versions: 1.2.0 > Environment: teiid-spring-boot > Reporter: Renat Eskenin > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > Attachments: TEIIDSB-127.zip > > > When we used management.server.port=8081 and server.port=8080 in spring boot properties we get exception > [2019-10-10 12:12:53,806 MSK] ERROR [test] org.teiid.PROCESSOR [restartedMain]: TEIID30019 Unexpected exception for request 8fPp+5AbzHhy.0 > java.lang.IllegalArgumentException: No registered data sources found > How can we change management port for spring actuator and do not broken Teiid? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5834) Class cast exception using web service with bind varables

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5834?page=com.atlassian.jira.plugin... ] Work on TEIID-5834 started by Steven Hawkins. --------------------------------------------- > Class cast exception using web service with bind varables > --------------------------------------------------------- > > Key: TEIID-5834 > URL: https://issues.jboss.org/browse/TEIID-5834 > Project: Teiid > Issue Type: Bug > Affects Versions: 11.1.2 > Reporter: Mike Higgins > Assignee: Steven Hawkins > Priority: Major > > I am using a restful web service, which works fine if literal values are used to constrain it. However, when I use bind variables, it gives me a traceback: > java.lang.ClassCastException: org.teiid.query.sql.lang.ImmutableCompareCriteria cannot be cast to org.teiid.query.sql.lang.AbstractSetCriteria > at org.teiid.query.processor.relational.DependentCriteriaProcessor.prepareCriteria(DependentCriteriaProcessor.java:352) > at org.teiid.query.processor.relational.DependentProcedureCriteriaProcessor.prepareNextCommand(DependentProcedureCriteriaProcessor.java:60) > at org.teiid.query.processor.relational.DependentProcedureExecutionNode.prepareNextCommand(DependentProcedureExecutionNode.java:88) > at org.teiid.query.processor.relational.PlanExecutionNode.open(PlanExecutionNode.java:79) > at org.teiid.query.processor.relational.DependentProcedureExecutionNode.open(DependentProcedureExecutionNode.java:108) > at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) > at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) > at org.teiid.query.processor.relational.JoinStrategy.openRight(JoinStrategy.java:101) > at org.teiid.query.processor.relational.JoinNode.nextBatchDirectInternal(JoinNode.java:256) > at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:200) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) > at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:141) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:148) > 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:492) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:362) > ... 8 more > The SQL is: > SELECT CAIMANM.LM_BIOLOGICAL_SYSTEM."BIOLOGICAL_SYSTEM_UID", > WS_CLUSTER.WS_CLUSTER_T."VH_SPECIES", > WS_CLUSTER.WS_CLUSTER_T."PROJECT_SHORT_NAME", > WS_CLUSTER.WS_CLUSTER_T."biosysid" > FROM caimanm.lm_biological_system > LEFT OUTER JOIN WS_cluster.WS_cluster_t > ON (CAIMANM.LM_BIOLOGICAL_SYSTEM."BIOLOGICAL_SYSTEM_UID" = WS_CLUSTER.WS_CLUSTER_T."biosysid") > AND (WS_CLUSTER.WS_CLUSTER_T."biosysid" in (?, ?, ?)) > WHERE (CAIMANM.LM_BIOLOGICAL_SYSTEM."BIOLOGICAL_SYSTEM_UID" in (?, ?, ?)) > Where WS_CLUSTER is the web service. I didn't find any issues about this so I was not sure if a later version would work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-110) Support kerberos over pg/jdbc

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-110?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-110: --------------------------------- Fix Version/s: (was: 1.3.0) > Support kerberos over pg/jdbc > ----------------------------- > > Key: TEIIDSB-110 > URL: https://issues.jboss.org/browse/TEIIDSB-110 > Project: Teiid Spring Boot > Issue Type: Enhancement > Reporter: Steven Hawkins > Priority: Major > > Keycloak has support for spengo/kerberos, but at first glance it's only for browser/http challenge flows. It seems like using it in a direct flow is not possible out of the box: https://issues.jboss.org/browse/KEYCLOAK-1751 > Note that even if just kerberos password authentication were supported that would allow for secure logins without ssl, which can be useful for our pg transport. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-125) Provide source support Amazon Redshift

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-125?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIIDSB-125. ---------------------------------- Resolution: Duplicate Issue > Provide source support Amazon Redshift > -------------------------------------- > > Key: TEIIDSB-125 > URL: https://issues.jboss.org/browse/TEIIDSB-125 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.0 > > > Provide translator support for Amazon Redshift -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 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 2019