May 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5508) Add community docs around openshift usage

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5508?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5508. ----------------------------------- Fix Version/s: (was: 12.2) Resolution: Out of Date We provide some docker guidance. Beyond that we'll want people to use either spring boot or thorntail. > Add community docs around openshift usage > ----------------------------------------- > > Key: TEIID-5508 > URL: https://issues.jboss.org/browse/TEIID-5508 > Project: Teiid > Issue Type: Quality Risk > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > > We should expand upon docker dealing with running Teiid in a container to reference more about running in openshift - in particular how that affects cluster, load balancing, what health checks can be used, etc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3522) Provide Data Aggregation Extension to OData V4

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-3522?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3522: ---------------------------------- Fix Version/s: 12.3 (was: 12.2) > Provide Data Aggregation Extension to OData V4 > ---------------------------------------------- > > Key: TEIID-3522 > URL: https://issues.jboss.org/browse/TEIID-3522 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > OData V4 specification defines extension for Data Aggregation http://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/cs01/oda... > Teiid should provide support for this extension. There is Olingo support on this yet. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

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 Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5545?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5545: ---------------------------------- Fix Version/s: 12.2 (was: 12.3) > 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.2 > > > 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)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5735) Update Olingo library to 4.6.0

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5735?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-5735: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Update Olingo library to 4.6.0 > ------------------------------ > > Key: TEIID-5735 > URL: https://issues.jboss.org/browse/TEIID-5735 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.2 > > > Apache Olingo 4.6 released, to pick up changes update to the new version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5735) Update Olingo library to 4.6.0

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5735?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5735: --------------------------------------- Any chance they could respin to fix a transaction handling issue with change sets? > Update Olingo library to 4.6.0 > ------------------------------ > > Key: TEIID-5735 > URL: https://issues.jboss.org/browse/TEIID-5735 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > Apache Olingo 4.6 released, to pick up changes update to the new version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5735) Update Olingo library to 4.6.0

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5735: ----------------------------------- Summary: Update Olingo library to 4.6.0 Key: TEIID-5735 URL: https://issues.jboss.org/browse/TEIID-5735 Project: Teiid Issue Type: Task Components: Build/Kits Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 12.2 Apache Olingo 4.6 released, to pick up changes update to the new version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5734) Planning errors with masking due to unaliased column references

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5734?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-5734 at 5/3/19 9:59 AM: --------------------------------------------------------------- Corrected by also applying the re-aliasing logic to the condition for masking. A workaround is to not use a condition, but a full masking expression: {code} <mask order="0">case when vw.employee.id>2 then 'Blocked' else vw.employee.taxid end</mask> {code} was (Author: shawkins): Corrected by also applying the re-aliasing logic to the condition for masking. A workaround is to not use a condition, but a full masking expression: {code} <condition>case when vw.employee.id>2 then 'Blocked' else vw.employee.taxid end</condition> {code} > Planning errors with masking due to unaliased column references > --------------------------------------------------------------- > > Key: TEIID-5734 > URL: https://issues.jboss.org/browse/TEIID-5734 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 12.2, 11.2.3, 12.1.2 > > > The ColumnMaskingHelper is creating expressions using the unaliased source name. This implicitly is relying on other logic, such as the raising of an access node to compensate for that. If however a view layer with masking is used that has no access nodes or cannot be removed, then exceptions will occur if it appears in the user query aliased and with constructs above, such as an order by. > For example with the vdb: > {code} > <?xml version="1.0" encoding="UTF-8" standalone="no"?> > <vdb name="odatacm" version="1"> > <description>Test column masking for Odata </description> > <property name="validationDateTime" value="Thu May 02 14:13:21 CDT 2019"/> > <property name="validationVersion" value="8.12.13"/> > <model name="vw" type="VIRTUAL"> > <metadata type="DDL"><![CDATA[ > CREATE VIEW employee ( > id integer, > name string, > taxid string, > taxid_cd string, > CONSTRAINT pk_id PRIMARY KEY(id) > ) OPTIONS(UPDATABLE 'TRUE') > AS > SELECT > 1 AS id, 'Debbie' AS name, '123456789' AS taxid, 'SSN' AS taxid_cd > UNION > SELECT > 2 AS id, 'Mide' AS name, '234567891' AS taxid, 'FED' AS taxid_cd > UNION > SELECT > 3 AS id, 'DJS' AS name, '345678912' AS taxid, 'FED' AS taxid_cd > UNION > SELECT > 4 AS id, 'Joe' AS name, '456789123' AS taxid, 'SSN' AS taxid_cd; > ]]></metadata> > </model> > <data-role allow-create-temporary-tables="false" any-authenticated="true" grant-all="false" name="Data Role 1"> > <description/> > <permission> > <resource-name>vw.employee.taxid</resource-name> > <condition>vw.employee.id>2</condition> > <mask order="0">'Blocked'</mask> > </permission> > <permission> > <resource-name>vw</resource-name> > <allow-create>false</allow-create> > <allow-read>true</allow-read> > <allow-update>false</allow-update> > <allow-delete>false</allow-delete> > <allow-execute>false</allow-execute> > <allow-alter>false</allow-alter> > </permission> > <permission> > <resource-name>sysadmin</resource-name> > <allow-create>false</allow-create> > <allow-read>false</allow-read> > <allow-update>false</allow-update> > <allow-delete>false</allow-delete> > <allow-execute>false</allow-execute> > <allow-alter>false</allow-alter> > </permission> > </data-role> > </vdb> > {code} > and the query "select * from employee as e order by id" is issued, then an exception will be returned: > TEIID30259 Cannot introduce new expressions [vw.employee.id] in duplicate removal > Which is a safe guard to prevent further planning errors - note the unaliased / fully qualified name in the exception message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5734) Planning errors with masking due to unaliased column references

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5734?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5734. ----------------------------------- Resolution: Done Corrected by also applying the re-aliasing logic to the condition for masking. A workaround is to not use a condition, but a full masking expression: {code} <condition>case when vw.employee.id>2 then 'Blocked' else vw.employee.taxid end</condition> {code} > Planning errors with masking due to unaliased column references > --------------------------------------------------------------- > > Key: TEIID-5734 > URL: https://issues.jboss.org/browse/TEIID-5734 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 12.2, 11.2.3, 12.1.2 > > > The ColumnMaskingHelper is creating expressions using the unaliased source name. This implicitly is relying on other logic, such as the raising of an access node to compensate for that. If however a view layer with masking is used that has no access nodes or cannot be removed, then exceptions will occur if it appears in the user query aliased and with constructs above, such as an order by. > For example with the vdb: > {code} > <?xml version="1.0" encoding="UTF-8" standalone="no"?> > <vdb name="odatacm" version="1"> > <description>Test column masking for Odata </description> > <property name="validationDateTime" value="Thu May 02 14:13:21 CDT 2019"/> > <property name="validationVersion" value="8.12.13"/> > <model name="vw" type="VIRTUAL"> > <metadata type="DDL"><![CDATA[ > CREATE VIEW employee ( > id integer, > name string, > taxid string, > taxid_cd string, > CONSTRAINT pk_id PRIMARY KEY(id) > ) OPTIONS(UPDATABLE 'TRUE') > AS > SELECT > 1 AS id, 'Debbie' AS name, '123456789' AS taxid, 'SSN' AS taxid_cd > UNION > SELECT > 2 AS id, 'Mide' AS name, '234567891' AS taxid, 'FED' AS taxid_cd > UNION > SELECT > 3 AS id, 'DJS' AS name, '345678912' AS taxid, 'FED' AS taxid_cd > UNION > SELECT > 4 AS id, 'Joe' AS name, '456789123' AS taxid, 'SSN' AS taxid_cd; > ]]></metadata> > </model> > <data-role allow-create-temporary-tables="false" any-authenticated="true" grant-all="false" name="Data Role 1"> > <description/> > <permission> > <resource-name>vw.employee.taxid</resource-name> > <condition>vw.employee.id>2</condition> > <mask order="0">'Blocked'</mask> > </permission> > <permission> > <resource-name>vw</resource-name> > <allow-create>false</allow-create> > <allow-read>true</allow-read> > <allow-update>false</allow-update> > <allow-delete>false</allow-delete> > <allow-execute>false</allow-execute> > <allow-alter>false</allow-alter> > </permission> > <permission> > <resource-name>sysadmin</resource-name> > <allow-create>false</allow-create> > <allow-read>false</allow-read> > <allow-update>false</allow-update> > <allow-delete>false</allow-delete> > <allow-execute>false</allow-execute> > <allow-alter>false</allow-alter> > </permission> > </data-role> > </vdb> > {code} > and the query "select * from employee as e order by id" is issued, then an exception will be returned: > TEIID30259 Cannot introduce new expressions [vw.employee.id] in duplicate removal > Which is a safe guard to prevent further planning errors - note the unaliased / fully qualified name in the exception message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5734) Planning errors with masking due to unaliased column references

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5734: ------------------------------------- Summary: Planning errors with masking due to unaliased column references Key: TEIID-5734 URL: https://issues.jboss.org/browse/TEIID-5734 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.1.2, 12.2, 11.2.3 The ColumnMaskingHelper is creating expressions using the unaliased source name. This implicitly is relying on other logic, such as the raising of an access node to compensate for that. If however a view layer with masking is used that has no access nodes or cannot be removed, then exceptions will occur if it appears in the user query aliased and with constructs above, such as an order by. For example with the vdb: {code} <?xml version="1.0" encoding="UTF-8" standalone="no"?> <vdb name="odatacm" version="1"> <description>Test column masking for Odata </description> <property name="validationDateTime" value="Thu May 02 14:13:21 CDT 2019"/> <property name="validationVersion" value="8.12.13"/> <model name="vw" type="VIRTUAL"> <metadata type="DDL"><![CDATA[ CREATE VIEW employee ( id integer, name string, taxid string, taxid_cd string, CONSTRAINT pk_id PRIMARY KEY(id) ) OPTIONS(UPDATABLE 'TRUE') AS SELECT 1 AS id, 'Debbie' AS name, '123456789' AS taxid, 'SSN' AS taxid_cd UNION SELECT 2 AS id, 'Mide' AS name, '234567891' AS taxid, 'FED' AS taxid_cd UNION SELECT 3 AS id, 'DJS' AS name, '345678912' AS taxid, 'FED' AS taxid_cd UNION SELECT 4 AS id, 'Joe' AS name, '456789123' AS taxid, 'SSN' AS taxid_cd; ]]></metadata> </model> <data-role allow-create-temporary-tables="false" any-authenticated="true" grant-all="false" name="Data Role 1"> <description/> <permission> <resource-name>vw.employee.taxid</resource-name> <condition>vw.employee.id>2</condition> <mask order="0">'Blocked'</mask> </permission> <permission> <resource-name>vw</resource-name> <allow-create>false</allow-create> <allow-read>true</allow-read> <allow-update>false</allow-update> <allow-delete>false</allow-delete> <allow-execute>false</allow-execute> <allow-alter>false</allow-alter> </permission> <permission> <resource-name>sysadmin</resource-name> <allow-create>false</allow-create> <allow-read>false</allow-read> <allow-update>false</allow-update> <allow-delete>false</allow-delete> <allow-execute>false</allow-execute> <allow-alter>false</allow-alter> </permission> </data-role> </vdb> {code} and the query "select * from employee as e order by id" is issued, then an exception will be returned: TEIID30259 Cannot introduce new expressions [vw.employee.id] in duplicate removal Which is a safe guard to prevent further planning errors - note the unaliased / fully qualified name in the exception message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-81) Support Keycloak based OpenID authentication for pg/jdbc

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-81?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIIDSB-81. ----------------------------------- Resolution: Done Marking as resolved with latest changes that update the example as well. > Support Keycloak based OpenID authentication for pg/jdbc > -------------------------------------------------------- > > Key: TEIIDSB-81 > URL: https://issues.jboss.org/browse/TEIIDSB-81 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.1.0 > > > Support authentication for pg/jdbc through keycloak/rh-sso. Needs to use the authorization paradigm as TEIIDSB-63. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2019