April 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5731) Recursive Query Common Table Expressions (CTE) PostgreSQL

by Kolmar Vasconcelos (Jira)

[ https://issues.jboss.org/browse/TEIID-5731?page=com.atlassian.jira.plugin... ] Kolmar Vasconcelos closed TEIID-5731. ------------------------------------- Fix Version/s: 12.1.1 Resolution: Done My bad. I just cast the literal null and it worked. > Recursive Query Common Table Expressions (CTE) PostgreSQL > --------------------------------------------------------- > > Key: TEIID-5731 > URL: https://issues.jboss.org/browse/TEIID-5731 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 12.1.1 > Environment: Ubuntu Linux 18.04 > DBeaver 5.3.3 > TEIID JDBC 12.1.1 > Reporter: Kolmar Vasconcelos > Assignee: Steven Hawkins > Priority: Critical > Fix For: 12.1.1 > > > I'm trying to a recursive Common Table Expressions on my organization's VBL. I know it runs on top of PostgreSQL. I'm not responsible for the implementation, I'm just trying to access the data for Data Analysis. When I try to create the Recursive Query it gives me the error: Remote org.postgresql.util.PSQLException: ERROR: recursive query "cte" column 6 has type character varying(255) in non-recursive term but type character varying overall. > The problem is with the Null value. I can't CAST Null to VARCHAR. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5731) Recursive Query Common Table Expressions (CTE) PostgreSQL

by Kolmar Vasconcelos (Jira)

[ https://issues.jboss.org/browse/TEIID-5731?page=com.atlassian.jira.plugin... ] Kolmar Vasconcelos updated TEIID-5731: -------------------------------------- Description: I'm trying to a recursive Common Table Expressions on my organization's VBL. I know it runs on top of PostgreSQL. I'm not responsible for the implementation, I'm just trying to access the data for Data Analysis. When I try to create the Recursive Query it gives me the error: Remote org.postgresql.util.PSQLException: ERROR: recursive query "cte" column 6 has type character varying(255) in non-recursive term but type character varying overall. The problem is with the Null value. I can't CAST Null to VARCHAR. was: I'm trying to a recursive Common Table Expressions on my organization's VBL. I know it runs on top of PostgreSQL. I'm not responsible for the implementation, I'm just trying to access the data for Data Analysis. When I try to create the Recursive Query it gives me the error: Remote org.postgresql.util.PSQLException: ERROR: recursive query "cte" column 6 has type character varying(255) in non-recursive term but type character varying overall. The problem is with the Null value. I just can't CAST Null to VARCHAR. > Recursive Query Common Table Expressions (CTE) PostgreSQL > --------------------------------------------------------- > > Key: TEIID-5731 > URL: https://issues.jboss.org/browse/TEIID-5731 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 12.1.1 > Environment: Ubuntu Linux 18.04 > DBeaver 5.3.3 > TEIID JDBC 12.1.1 > Reporter: Kolmar Vasconcelos > Assignee: Steven Hawkins > Priority: Critical > > I'm trying to a recursive Common Table Expressions on my organization's VBL. I know it runs on top of PostgreSQL. I'm not responsible for the implementation, I'm just trying to access the data for Data Analysis. When I try to create the Recursive Query it gives me the error: Remote org.postgresql.util.PSQLException: ERROR: recursive query "cte" column 6 has type character varying(255) in non-recursive term but type character varying overall. > The problem is with the Null value. I can't CAST Null to VARCHAR. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5731) Recursive Query Common Table Expressions (CTE) PostgreSQL

by Kolmar Vasconcelos (Jira)

Kolmar Vasconcelos created TEIID-5731: ----------------------------------------- Summary: Recursive Query Common Table Expressions (CTE) PostgreSQL Key: TEIID-5731 URL: https://issues.jboss.org/browse/TEIID-5731 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 12.1.1 Environment: Ubuntu Linux 18.04 DBeaver 5.3.3 TEIID JDBC 12.1.1 Reporter: Kolmar Vasconcelos Assignee: Steven Hawkins I'm trying to a recursive Common Table Expressions on my organization's VBL. I know it runs on top of PostgreSQL. I'm not responsible for the implementation, I'm just trying to access the data for Data Analysis. When I try to create the Recursive Query it gives me the error: Remote org.postgresql.util.PSQLException: ERROR: recursive query "cte" column 6 has type character varying(255) in non-recursive term but type character varying overall. The problem is with the Null value. I just can't CAST Null to VARCHAR. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-84) There needs to be an error page

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-84: ------------------------------------- Summary: There needs to be an error page Key: TEIIDSB-84 URL: https://issues.jboss.org/browse/TEIIDSB-84 Project: Teiid Spring Boot Issue Type: Quality Risk Components: OData Reporter: Steven Hawkins Fix For: 1.1.0 If you try a url, such as /foo it results in a lengthy log: 2019-04-30 15:20:14.247 ERROR 14280 --- [nio-8080-exec-2] o.a.c.c.C.[Tomcat].[localhost] : Exception Processing ErrorPage[errorCode=0, location=/error] javax.servlet.ServletException: Circular view path [error]: would dispatch back to the current handler URL [/error] again. Check your ViewResolver setup! (Hint: This may be the result of an unspecified view, due to default view name generation.) at org.springframework.web.servlet.view.InternalResourceView.prepareForRendering(InternalResourceView.java:209) ~[spring-webmvc-5.1.4.RELEASE.jar!/:5.1.4.RELEASE] at org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:147) ~[spring-webmvc-5.1.4.RELEASE.jar!/:5.1.4.RELEASE] at org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:316) ~[spring-webmvc-5.1.4.RELEASE.jar!/:5.1.4.RELEASE] at org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1370) ~[spring-webmvc-5.1.4.RELEASE.jar!/:5.1.4.RELE... -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-44) Support JDBC/ODBC security using Keycloak

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-44?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIIDSB-44. --------------------------------- Resolution: Duplicate Issue > Support JDBC/ODBC security using Keycloak > ----------------------------------------- > > Key: TEIIDSB-44 > URL: https://issues.jboss.org/browse/TEIIDSB-44 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: core > Reporter: Ramesh Reddy > Priority: Major > > JDBC or ODBC there is no security defined when using these protocols. Security options need to be investigated using Keycloak as the auth provider. This can be a simple user/password or Kerberos based authentication/authorization support. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-47) Determine behavior of alter statements

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-47?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIIDSB-47. --------------------------------- Resolution: Done Added the flag to control the allowance of allowAlter property to be set on TSB. By default, it is set to false. > Determine behavior of alter statements > -------------------------------------- > > Key: TEIIDSB-47 > URL: https://issues.jboss.org/browse/TEIIDSB-47 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > The engine allows alter statements to ephemerally (by default) change view definitions, turn on/off triggers, etc. For Spring Boot and OpenShift deployment in particular we should consider whether this should be allowable/optional behavior. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5545) Odata V4 Batch processing does not work as teiid/olingo rejects "Accept: multipart/mixed" request header

by Christoph John (Jira)

[ https://issues.jboss.org/browse/TEIID-5545?page=com.atlassian.jira.plugin... ] Christoph John commented on TEIID-5545: --------------------------------------- Great news :) > Odata V4 Batch processing does not work as teiid/olingo rejects "Accept: multipart/mixed" request header > -------------------------------------------------------------------------------------------------------- > > Key: TEIID-5545 > URL: https://issues.jboss.org/browse/TEIID-5545 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 11.2 > Reporter: Christoph John > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 12.3 > > > When using Teiid together with SAPUI5/OpenUI5 Odata V4 model, batch processing does not work as Teiid rejects the "Accept: multipart/mixed" header. The issue has been described in > https://developer.jboss.org/message/986421#986421 > It has been stated that Olingo in general does support multipart messages and it was recommended to remove the header from the request. > https://developer.jboss.org/message/986425#986425 > Unfortunately this seems to be not easily possible when using the SAPUI5 framework. I addressed the issue in the SAPUI5 forum under the following issue: > https://github.com/SAP/openui5/issues/2288 > The result of this discussion was, that the header is valid for the send content. As I am no expert in the topic I do not really have an opinion on that. However, > https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html > suggests that the header is required. So I am not sure if it is correct or an error to reject the message. However, if Olingo can process the content, it would be great to have a fix for the accept header, or alternatively a config option to enable handling of the Accept header in a way that Olingo processes these data. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-82) OData content should be served under a specific context

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-82?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIIDSB-82. --------------------------------- Resolution: Done Moved under "odata" by default. The URL always will be`[<context>?]/odata/$metadata` > OData content should be served under a specific context > ------------------------------------------------------- > > Key: TEIIDSB-82 > URL: https://issues.jboss.org/browse/TEIIDSB-82 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: OData > Affects Versions: 1.0.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Currently, OData documents are served at the root context, by default these should be limited to a context path such that collisions in the name can be avoided. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-82) OData content should be served under a specific context

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-82?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIIDSB-82: ----------------------------------- Assignee: Ramesh Reddy > OData content should be served under a specific context > ------------------------------------------------------- > > Key: TEIIDSB-82 > URL: https://issues.jboss.org/browse/TEIIDSB-82 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: OData > Affects Versions: 1.0.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Currently, OData documents are served at the root context, by default these should be limited to a context path such that collisions in the name can be avoided. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5545) Odata V4 Batch processing does not work as teiid/olingo rejects "Accept: multipart/mixed" request header

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5545?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5545: ------------------------------------- 4.6 will be available maybe within next 2 weeks. > Odata V4 Batch processing does not work as teiid/olingo rejects "Accept: multipart/mixed" request header > -------------------------------------------------------------------------------------------------------- > > Key: TEIID-5545 > URL: https://issues.jboss.org/browse/TEIID-5545 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 11.2 > Reporter: Christoph John > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 12.3 > > > When using Teiid together with SAPUI5/OpenUI5 Odata V4 model, batch processing does not work as Teiid rejects the "Accept: multipart/mixed" header. The issue has been described in > https://developer.jboss.org/message/986421#986421 > It has been stated that Olingo in general does support multipart messages and it was recommended to remove the header from the request. > https://developer.jboss.org/message/986425#986425 > Unfortunately this seems to be not easily possible when using the SAPUI5 framework. I addressed the issue in the SAPUI5 forum under the following issue: > https://github.com/SAP/openui5/issues/2288 > The result of this discussion was, that the header is valid for the send content. As I am no expert in the topic I do not really have an opinion on that. However, > https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html > suggests that the header is required. So I am not sure if it is correct or an error to reject the message. However, if Olingo can process the content, it would be great to have a fix for the accept header, or alternatively a config option to enable handling of the Accept header in a way that Olingo processes these data. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 12 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