April 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-75) Provide Salesforce source support

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-75?page=com.atlassian.jira.plugin... ] Ramesh Reddy deleted TEIIDSB-75: -------------------------------- > Provide Salesforce source support > --------------------------------- > > Key: TEIIDSB-75 > URL: https://issues.jboss.org/browse/TEIIDSB-75 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > > Salesforce data source needs to be supported. Should support the same authentication as the Syndesis -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-75) Provide Salesforce source support

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-75: ----------------------------------- Summary: Provide Salesforce source support Key: TEIIDSB-75 URL: https://issues.jboss.org/browse/TEIIDSB-75 Project: Teiid Spring Boot Issue Type: Feature Request Components: datasource Affects Versions: 1.1.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Salesforce data source needs to be supported. Should support the same authentication as the Syndesis -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5722) Built in support for Postgres DB as materialization target

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5722?page=com.atlassian.jira.plugin... ] Ramesh Reddy deleted TEIID-5722: -------------------------------- > Built in support for Postgres DB as materialization target > ---------------------------------------------------------- > > Key: TEIID-5722 > URL: https://issues.jboss.org/browse/TEIID-5722 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > > If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like > - Creation of a common STATUS table > - Creation of the materilization targets (create views on dbms) > - On load, on undeploy and load scripts for all the materialization views > We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5722) Built in support for Postgres DB as materialization target

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5722: ----------------------------------- Summary: Built in support for Postgres DB as materialization target Key: TEIID-5722 URL: https://issues.jboss.org/browse/TEIID-5722 Project: Teiid Issue Type: Sub-task Components: Server Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 12.2 If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like - Creation of a common STATUS table - Creation of the materilization targets (create views on dbms) - On load, on undeploy and load scripts for all the materialization views We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-74) Provide rest access with SpringBoot

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-74: ----------------------------------- Summary: Provide rest access with SpringBoot Key: TEIIDSB-74 URL: https://issues.jboss.org/browse/TEIIDSB-74 Project: Teiid Spring Boot Issue Type: Feature Request Reporter: Ramesh Reddy Assignee: Ramesh Reddy The current rest access layer is based upon the generation of a war with deployment hooks in wildfly. There should be a build-time or similar mechanism to expose rest with spring boot. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-73) Support Keycloak based OpenID authentication for OData Through 3scale

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-73: ----------------------------------- Summary: Support Keycloak based OpenID authentication for OData Through 3scale Key: TEIIDSB-73 URL: https://issues.jboss.org/browse/TEIIDSB-73 Project: Teiid Spring Boot Issue Type: Feature Request Reporter: Ramesh Reddy Support the authentication for OData through 3scale -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5721) Subquery join - Planning error. Could not find symbol

by Mark Tawk (Jira)

Mark Tawk created TEIID-5721: -------------------------------- Summary: Subquery join - Planning error. Could not find symbol Key: TEIID-5721 URL: https://issues.jboss.org/browse/TEIID-5721 Project: Teiid Issue Type: Bug Reporter: Mark Tawk Assignee: Steven Hawkins Attachments: teiidError.txt I have an issue happening on a specific query containing subquery joins and I am getting the exception: org.teiid.core.TeiidRuntimeException: Planning error. Could not find symbol... you find attached the exception error along with the query SQL and the query plan. Reproduced on Teiid version 10.2.1 and the latest version -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-64) Research HA

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-64?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIIDSB-64 at 4/11/19 10:58 PM: ----------------------------------------------------------------- Also it looks like we'll want to set service.spec.sessionAffinityConfig.clientIP.timeoutSecond for pg/jdbc - the default is 10800 seconds or 3 hours. The maximum is 86400 or 24 hours, so that introduces a hard limit on session life if using more than one replica. was (Author: shawkins): Also it looks like we'll want to set service.spec.sessionAffinityConfig.clientIP.timeoutSecond for pg/jdbc - the default is 10800 seconds or 3 hours. > Research HA > ----------- > > Key: TEIIDSB-64 > URL: https://issues.jboss.org/browse/TEIIDSB-64 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > > Teiid's pg, and jdbc assume session affinity. Also OData pagination works best with session affinity. > For HA, and horizontal scaling, it would be good to have more than 1 pod alive and receiving traffic. It appears that there is a sessionAffinity setting at a service level https://kubernetes.io/docs/concepts/services-networking/service/ and some work that can be done to customize routes https://docs.openshift.com/container-platform/3.9/architecture/networking... - but that doesn't appear to work for just tcp traffic. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-64) Research HA

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-64?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-64: --------------------------------------- Also it looks like we'll want to set service.spec.sessionAffinityConfig.clientIP.timeoutSecond for pg/jdbc - the default is 10800 seconds or 3 hours. > Research HA > ----------- > > Key: TEIIDSB-64 > URL: https://issues.jboss.org/browse/TEIIDSB-64 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > > Teiid's pg, and jdbc assume session affinity. Also OData pagination works best with session affinity. > For HA, and horizontal scaling, it would be good to have more than 1 pod alive and receiving traffic. It appears that there is a sessionAffinity setting at a service level https://kubernetes.io/docs/concepts/services-networking/service/ and some work that can be done to customize routes https://docs.openshift.com/container-platform/3.9/architecture/networking... - but that doesn't appear to work for just tcp traffic. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-72) Support Keycloak based OpenID authentication for OData Through 3scale

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-72: ----------------------------------- Summary: Support Keycloak based OpenID authentication for OData Through 3scale Key: TEIIDSB-72 URL: https://issues.jboss.org/browse/TEIIDSB-72 Project: Teiid Spring Boot Issue Type: Feature Request Reporter: Ramesh Reddy Support the authentication for OData through 3scale -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2019