April 2019 - teiid-issues - Jboss List Archives

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

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5721?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5721. ----------------------------------- Resolution: Done The last fix TEIID-5636 did not go far enough in correcting the groups of parent nodes. > Subquery join - Planning error. Could not find symbol > ----------------------------------------------------- > > Key: TEIID-5721 > URL: https://issues.jboss.org/browse/TEIID-5721 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2, 11.2.3, 12.1.1 > > 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] (TEIID-5721) Subquery join - Planning error. Could not find symbol

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5721?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5721: ---------------------------------- Component/s: Query Engine Fix Version/s: 12.2 11.2.3 12.1.1 > Subquery join - Planning error. Could not find symbol > ----------------------------------------------------- > > Key: TEIID-5721 > URL: https://issues.jboss.org/browse/TEIID-5721 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2, 11.2.3, 12.1.1 > > 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-54) Provide Salesforce source support

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-54?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIIDSB-54 at 4/15/19 3:38 PM: -------------------------------------------------------------- Added support for Salesforce as a data source in TSB runtime. It supports both password-based and refresh-token based authentications with Salesforce which is compatible with Syndesis. was (Author: rareddy): Added support for Salesdorce as datasource in TSB runtime. It supports both password based and refresh-token based authentications with Salesforce which is compatible with Syndesis. > Provide Salesforce source support > --------------------------------- > > Key: TEIIDSB-54 > URL: https://issues.jboss.org/browse/TEIIDSB-54 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Affects Versions: 1.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > 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-54) Provide Salesforce source support

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-54?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIIDSB-54. --------------------------------- Fix Version/s: 1.1.0 Resolution: Done Added support for Salesdorce as datasource in TSB runtime. It supports both password based and refresh-token based authentications with Salesforce which is compatible with Syndesis. > Provide Salesforce source support > --------------------------------- > > Key: TEIIDSB-54 > URL: https://issues.jboss.org/browse/TEIIDSB-54 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Affects Versions: 1.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > 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-53) Provide Preparser support

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-53?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIIDSB-53. --------------------------------- Resolution: Done Provide a Bean with PreParser interface to be picked up for example: {code} @Bean public PreParser myInterceptor(){ return new PreParser() { public String preParse(String command, CommandContext context) { // do your customization } }; } {code} > Provide Preparser support > ------------------------- > > Key: TEIIDSB-53 > URL: https://issues.jboss.org/browse/TEIIDSB-53 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: core > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > There is no Pre Parser support for migrating users. Support needs to be provided -- 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 Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5721?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5721: --------------------------------------- I have reproduced this. The issue is with the run of rule plan outer joins prior to join planning. I should be able to address it today. > 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 > Priority: Major > 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] (TEIID-5721) Subquery join - Planning error. Could not find symbol

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5721?page=com.atlassian.jira.plugin... ] Work on TEIID-5721 started by Steven Hawkins. --------------------------------------------- > 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 > Priority: Major > 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 resolved TEIIDSB-64. ----------------------------------- Fix Version/s: 1.1.0 Resolution: Done Updated the example and detailed finding on this issue. > 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 > Fix For: 1.1.0 > > > 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: --------------------------------------- The docs are little confusing on this, but a loadbalancer selector does not seem to work well against a service name. If you use app/dc it works fine: {code} oc create -f - <<INGRESS apiVersion: v1 kind: Service metadata: name: rdbms-example-ingress spec: ports: - name: teiid port: 31000 type: LoadBalancer selector: app: rdbms-example sessionAffinity: ClientIP INGRESS {code} We want to use the app directly in any case as the internal services themselves will be set to have ClientIP sessionAffinity - so using the internal service would mean that all of the external load balanced traffic would go to a single pod. I'll see how/if this can be incorporated in the example. > 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: --------------------------------------- Here's a good overview: https://docs.openshift.com/container-platform/3.9/dev_guide/expose_servic... The options are: - NodePort - https://access.redhat.com/solutions/3920661 - I don't think this should be promoted as a solution as it's pretty low level. It requires you to determine the extneral node ips of the nodes where the service is running. - TLS with SNI - by default will require the traffic to go through port 443. Requires passthrough encryption, which means all traffic will be encrypted unless two transports are opened (JDBC). Does not work for the pg protocol as it is not end to end TLS, instead it is negotiated post connection. - A better NodePort solution is a LoadBalancer service - See https://docs.openshift.com/container-platform/3.9/dev_guide/expose_servic... and https://docs.openshift.com/container-platform/3.10/admin_guide/tcp_ingres... it can be created with just two commands or added to our templates. Note that the external ip can be confusing. There is a default value based upon ingressIPNetworkCIDR, but there are some doc issue https://github.com/openshift/openshift-docs/issues/11024 The simplest thing for minishift is to just use the console ip. Tested with pg. A downside is that you don't control the exposed node port. I'll do some testing with Teiid and determine how this interacts with the service level session affinity. - External IP - I haven't spent much time on that as it appears more involved. > 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2019