July 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5780) Support certificate based authentication into Teiid pg

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5780?page=com.atlassian.jira.plugi... ] Work on TEIID-5780 started by Steven Hawkins. --------------------------------------------- > Support certificate based authentication into Teiid pg > ------------------------------------------------------ > > Key: TEIID-5780 > URL: https://issues.redhat.com/browse/TEIID-5780 > Project: Teiid > Issue Type: Sub-task > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 2 days > Time Spent: 6 hours > Remaining Estimate: 1 day, 2 hours > > To support the pg connection into Teiid we will do something like: > - require a pg secure port using the service signing certificate: TEIIDSB-90 TEIIDSB-92 > -- one clarification is that we must document how to make the pg cert dominant if both pg and jdbc secure are used > TODO: > - configure the pg instance to have a service signing certificate and trust the Teiid service signing certificate. If that trust seems too difficult we can just configure the connection to trust all. > - configure the pg connection to Teiid to use the pg service signing certificate as the client certificate > - trust the pg service signing certificate at the teiid service - we need hostname validation to be enabled and the Teiid server to map the service host name to an authenticated user (this could possibly be generalized via keycloak support to more users). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5838) Add a vdb/source metadata load timeout

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5838?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5838: ---------------------------------- Fix Version/s: Backlog (was: 15.0) > Add a vdb/source metadata load timeout > -------------------------------------- > > Key: TEIID-5838 > URL: https://issues.redhat.com/browse/TEIID-5838 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: Backlog > > > Source vdb loads should timeout to prevent refresh and other issues. > Note: this may be implemented in core Teiid, in which case this issue will be moved. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-6002) Support cloudera hue access as pg

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-6002?focusedWorklogId=12451833&pag... ] Steven Hawkins logged work on TEIID-6002: ----------------------------------------- Author: Steven Hawkins Created on: 29/Jul/20 10:20 AM Start Date: 29/Jul/20 10:20 AM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 2 hours) Time Spent: 2 hours Worklog Id: (was: 12451833) > Support cloudera hue access as pg > --------------------------------- > > Key: TEIID-6002 > URL: https://issues.redhat.com/browse/TEIID-6002 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0, 14.0.1 > > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Hue uses pg_tables: https://github.com/cloudera/hue/blob/4ff4fb110c3ef40fe202a50d81cb94fb98eb... > Rather than just pg class like most clients/drivers. We should add that view to the pg_catalog. > Everything else looks to be supported. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-6002) Support cloudera hue access as pg

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-6002?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-6002: ---------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > Support cloudera hue access as pg > --------------------------------- > > Key: TEIID-6002 > URL: https://issues.redhat.com/browse/TEIID-6002 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0, 14.0.1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Hue uses pg_tables: https://github.com/cloudera/hue/blob/4ff4fb110c3ef40fe202a50d81cb94fb98eb... > Rather than just pg class like most clients/drivers. We should add that view to the pg_catalog. > Everything else looks to be supported. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-6002) Support cloudera hue access as pg

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-6002?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-6002. ----------------------------------- Fix Version/s: 15.0 14.0.1 Resolution: Done Adding support for pg_tables. For whatever reason hue is only interested in table metadata - no views. It uses pg_tables rather than pg_class where relkind = 'r'. > Support cloudera hue access as pg > --------------------------------- > > Key: TEIID-6002 > URL: https://issues.redhat.com/browse/TEIID-6002 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0, 14.0.1 > > > Hue uses pg_tables: https://github.com/cloudera/hue/blob/4ff4fb110c3ef40fe202a50d81cb94fb98eb... > Rather than just pg class like most clients/drivers. We should add that view to the pg_catalog. > Everything else looks to be supported. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5949) SQLServer DateTimeOffset datatype is read as object(34)

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5949?focusedWorklogId=12451827&pag... ] Steven Hawkins logged work on TEIID-5949: ----------------------------------------- Author: Steven Hawkins Created on: 28/Jul/20 5:56 PM Start Date: 28/Jul/20 5:55 PM Worklog Time Spent: 1 hour, 30 minutes Work Description: Took a little longer than expected to get a sql server environment up, needed to use the 2017 docker image to confirm the type name. Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 1 hour) Time Spent: 1 hour, 30 minutes Worklog Id: (was: 12451827) > SQLServer DateTimeOffset datatype is read as object(34) > ------------------------------------------------------- > > Key: TEIID-5949 > URL: https://issues.redhat.com/browse/TEIID-5949 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 11.1.2 > Reporter: Manoj Majumdar > Assignee: Steven Hawkins > Priority: Major > Labels: TEIID30504, sqlserver2012 > Fix For: 15.0, 14.0.1 > > Original Estimate: 1 hour > Time Spent: 1 hour, 30 minutes > Remaining Estimate: 0 minutes > > Hi, > I am trying to set null in datetimeoffset datatype of SQLSERVER using Teiid , but it is giving the error as: > org.teiid.jdbc.TeiidSQLException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 B_MSSQL1: S0003 Implicit conversion from data type varbinary to datetimeoffset is not allowed. Use the CONVERT function to run this query. > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:131) > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:67) > at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:752) > at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:62) > at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:562) > at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:131) > at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:36) > at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:75) > at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:281) > at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:333) > at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:423) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:571) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:420) > at org.teiid.jdbc.PreparedStatementImpl.executeBatch(PreparedStatementImpl.java:296) > I am just using a table, with only one column "datetimeoffset" and when I an using Preparedstatement.setNull(1, Types.TIMESTAMP), it is throwing this error. > Also the datetimeoffset datatype is read as "object(34)" while fetching the schema using Teiid and Microsoft JDBC driver. > Please suggest any ways to overcome this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5949) SQLServer DateTimeOffset datatype is read as object(34)

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5949?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5949: ---------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour Story Points: 0.1 Sprint: DV Sprint 66 > SQLServer DateTimeOffset datatype is read as object(34) > ------------------------------------------------------- > > Key: TEIID-5949 > URL: https://issues.redhat.com/browse/TEIID-5949 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 11.1.2 > Reporter: Manoj Majumdar > Assignee: Steven Hawkins > Priority: Major > Labels: TEIID30504, sqlserver2012 > Fix For: 15.0, 14.0.1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Hi, > I am trying to set null in datetimeoffset datatype of SQLSERVER using Teiid , but it is giving the error as: > org.teiid.jdbc.TeiidSQLException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 B_MSSQL1: S0003 Implicit conversion from data type varbinary to datetimeoffset is not allowed. Use the CONVERT function to run this query. > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:131) > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:67) > at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:752) > at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:62) > at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:562) > at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:131) > at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:36) > at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:75) > at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:281) > at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:333) > at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:423) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:571) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:420) > at org.teiid.jdbc.PreparedStatementImpl.executeBatch(PreparedStatementImpl.java:296) > I am just using a table, with only one column "datetimeoffset" and when I an using Preparedstatement.setNull(1, Types.TIMESTAMP), it is throwing this error. > Also the datetimeoffset datatype is read as "object(34)" while fetching the schema using Teiid and Microsoft JDBC driver. > Please suggest any ways to overcome this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5949) SQLServer DateTimeOffset datatype is read as object(34)

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5949?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5949. ----------------------------------- Fix Version/s: 14.0.1 Resolution: Done Updated the mapping to string based upon the comments here. We'll need to consider adding first class support for timestamp with timezone (although we'd need arbitrary offsets here) to better handle situations like this. > SQLServer DateTimeOffset datatype is read as object(34) > ------------------------------------------------------- > > Key: TEIID-5949 > URL: https://issues.redhat.com/browse/TEIID-5949 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 11.1.2 > Reporter: Manoj Majumdar > Assignee: Steven Hawkins > Priority: Major > Labels: TEIID30504, sqlserver2012 > Fix For: 15.0, 14.0.1 > > > Hi, > I am trying to set null in datetimeoffset datatype of SQLSERVER using Teiid , but it is giving the error as: > org.teiid.jdbc.TeiidSQLException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 B_MSSQL1: S0003 Implicit conversion from data type varbinary to datetimeoffset is not allowed. Use the CONVERT function to run this query. > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:131) > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:67) > at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:752) > at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:62) > at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:562) > at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:131) > at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:36) > at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:75) > at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:281) > at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:333) > at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:423) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:571) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:420) > at org.teiid.jdbc.PreparedStatementImpl.executeBatch(PreparedStatementImpl.java:296) > I am just using a table, with only one column "datetimeoffset" and when I an using Preparedstatement.setNull(1, Types.TIMESTAMP), it is throwing this error. > Also the datetimeoffset datatype is read as "object(34)" while fetching the schema using Teiid and Microsoft JDBC driver. > Please suggest any ways to overcome this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-6002) Support cloudera hue access as pg

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-6002: ------------------------------------- Summary: Support cloudera hue access as pg Key: TEIID-6002 URL: https://issues.redhat.com/browse/TEIID-6002 Project: Teiid Issue Type: Feature Request Components: ODBC Reporter: Steven Hawkins Assignee: Steven Hawkins Hue uses pg_tables: https://github.com/cloudera/hue/blob/4ff4fb110c3ef40fe202a50d81cb94fb98eb... Rather than just pg class like most clients/drivers. We should add that view to the pg_catalog. Everything else looks to be supported. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5928) Allow External and Internal materialization of multi-source to fail/update individually

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5928?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5928: ---------------------------------- Sprint: DV Sprint 66 > Allow External and Internal materialization of multi-source to fail/update individually > --------------------------------------------------------------------------------------- > > Key: TEIID-5928 > URL: https://issues.redhat.com/browse/TEIID-5928 > Project: Teiid > Issue Type: Enhancement > Components: Common > Affects Versions: 12.2.2 > Reporter: Rafael Sampaio > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 1 day, 4 hours > Time Spent: 1 day, 4 hours, 30 minutes > Remaining Estimate: 0 minutes > > Hi, all. > First of all thanks in advance for your attention, and efforts on such a great product. > Since I haven't found any docs or examples regarding my current usage (please if this already exists or there's a better way of doing this, disregard this request and advice) here goes my suggestion: > It would be nice to have a way to gracefully update/fail per source, if a view that has Materialization enabled and target a multi-source source model, because things can get, messy if I have to create a view per source and Materialize each one and only then create a unified (UNION) view. > Using this approach also obligates me to implement custom insert/update/delete/based on the discriminator column. > Thanks again. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2020