June 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-111) Security Context not being propagated in OData with Keycloak

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-111?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIIDSB-111. ---------------------------------- Resolution: Done > Security Context not being propagated in OData with Keycloak > ------------------------------------------------------------ > > Key: TEIIDSB-111 > URL: https://issues.jboss.org/browse/TEIIDSB-111 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core, OData, OpenShift > Affects Versions: 1.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 1.2.0, 7.4-1.1.1 > > > The security context not being propagated correctly from the web layer when passthrough authentication is set to true. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-112) Security Context not being propagated in OData with Keycloak

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-112: ------------------------------------ Summary: Security Context not being propagated in OData with Keycloak Key: TEIIDSB-112 URL: https://issues.jboss.org/browse/TEIIDSB-112 Project: Teiid Spring Boot Issue Type: Bug Components: core, OData, OpenShift Affects Versions: 1.1.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 1.2.0, 7.4-1.1.1 The security context not being propagated correctly from the web layer when passthrough authentication is set to true. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

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

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4251: --------------------------------------- In broad strokes we have two approaches, using the pg fdw, and updating our existing materialization logic. *pg fdw* Pros: * uses pg materialization logic, which includes support for background loads * uses the fdw import, which minimizes the ddl that we need to generate * does not require an xa source and the mvstatus function is not necessary (discussed more above) * automatically a "cluster-wise" mechanism as the load function is centralized Cons: * requires that the pg fdw connection into Teiid is some kind of admin ** one way to address this on openshift is to base this off of ssl, which requires a good bit of setup see TEIID-5780 * is not compatible with row level updates * has some restrictions on schema names * requires a lot of changes to the existing materialization procedures to map to pg functionality *existing materialization* Pros: * already exists :) which aligns to the existing procedures. * (mostly) handles additional status concepts such as wait and ignore. * allows for incremental updates Cons: * there are a couple of holes with our existing approach such as that the mvstatus function is best effort, and not transactionally safe. Mentioned in the last comment is the idea of moving the effect of the mvstatus function to pg (atomic) triggers so that things are safe. * not cluster-wise - we need new logic about stalled/abandoned loads in particular * we need full ddl generation support The second one is the thorniest issue. More than likely we'd need to centralize the load logic. Both approaches have similar issues with index generation. > Built in support for Postgres DB as materialization target > ---------------------------------------------------------- > > Key: TEIID-4251 > URL: https://issues.jboss.org/browse/TEIID-4251 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > 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)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-111) Security Context not being propagated in OData with Keycloak

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-111: ------------------------------------ Summary: Security Context not being propagated in OData with Keycloak Key: TEIIDSB-111 URL: https://issues.jboss.org/browse/TEIIDSB-111 Project: Teiid Spring Boot Issue Type: Bug Components: core, OData, OpenShift Affects Versions: 1.1.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 1.2.0, 7.4-1.1.1 The security context not being propagated correctly from the web layer when passthrough authentication is set to true. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

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

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4251: ------------------------------------- (y) interesting, a simple prototype should expose any issues. > Built in support for Postgres DB as materialization target > ---------------------------------------------------------- > > Key: TEIID-4251 > URL: https://issues.jboss.org/browse/TEIID-4251 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > 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)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5784) OData4 returns $metadata in JSON when "Accept" not specified

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5784?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-5784: -------------------------------- Summary: OData4 returns $metadata in JSON when "Accept" not specified (was: OData4 returns $metadata in JSON when contentType not specified) > OData4 returns $metadata in JSON when "Accept" not specified > ------------------------------------------------------------ > > Key: TEIID-5784 > URL: https://issues.jboss.org/browse/TEIID-5784 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors, OData > Affects Versions: 12.2 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.3 > > > with upgrade to Olingo 4.6, there is update to $metadata call that can return the content in JSON format. However OData4 translator can only parse the XML content. This occurs when "Accept" header is not specified with the request -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5784) OData4 returns $metadata in JSON when contentType not specified

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5784?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-5784: -------------------------------- Description: with upgrade to Olingo 4.6, there is update to $metadata call that can return the content in JSON format. However OData4 translator can only parse the XML content. This occurs when "Accept" header is not specified with the request (was: with upgrade to Olingo 4.6, there is update to $metadata call that can return the content in JSON format. However OData4 translator can only parse the XML content. This occurs when "content-type" header is not specified with the request) > OData4 returns $metadata in JSON when contentType not specified > --------------------------------------------------------------- > > Key: TEIID-5784 > URL: https://issues.jboss.org/browse/TEIID-5784 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors, OData > Affects Versions: 12.2 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.3 > > > with upgrade to Olingo 4.6, there is update to $metadata call that can return the content in JSON format. However OData4 translator can only parse the XML content. This occurs when "Accept" header is not specified with the request -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5784) OData4 returns $metadata in JSON when contentType not specified

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5784: ----------------------------------- Summary: OData4 returns $metadata in JSON when contentType not specified Key: TEIID-5784 URL: https://issues.jboss.org/browse/TEIID-5784 Project: Teiid Issue Type: Bug Components: Misc. Connectors, OData Affects Versions: 12.2 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 12.3 with upgrade to Olingo 4.6, there is update to $metadata call that can return the content in JSON format. However OData4 translator can only parse the XML content. This occurs when "content-type" header is not specified with the request -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5784) OData4 returns $metadata in JSON when contentType not specified

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5784?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-5784: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > OData4 returns $metadata in JSON when contentType not specified > --------------------------------------------------------------- > > Key: TEIID-5784 > URL: https://issues.jboss.org/browse/TEIID-5784 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors, OData > Affects Versions: 12.2 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.3 > > > with upgrade to Olingo 4.6, there is update to $metadata call that can return the content in JSON format. However OData4 translator can only parse the XML content. This occurs when "content-type" header is not specified with the request -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

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

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4251: --------------------------------------- Given the complexity of the ssl approach another possibility is to move the mvstatus logic to pg in the form of before triggers - that would remove the need for XA support to simplify things a little. > Built in support for Postgres DB as materialization target > ---------------------------------------------------------- > > Key: TEIID-4251 > URL: https://issues.jboss.org/browse/TEIID-4251 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > 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)

4 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2019