May 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5950) Create an athena translator

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5950: ------------------------------------- Summary: Create an athena translator Key: TEIID-5950 URL: https://issues.redhat.com/browse/TEIID-5950 Project: Teiid Issue Type: Enhancement Components: JDBC Connector Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 14.1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-192) Document migration for alias names

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-192?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-192: ---------------------------------------- The convention we have now is [something-]source where something is either a company or driver name. Other than ensuring Teiid Spring Boot documentation is aligned with the last set of changes, that just leaves us with Salesforce as an issue. It would be great if the user were abstracted from the implementation details of the translator/source - that is they would specify that salesforce connectivity to api version x is needed and then we'd select the appropriate translator / source version to support that (typically a given sf api library will support a range of api versions). However we haven't required the version to be specified (via the url) and there are obviously a lot of versions that we wouldn't support - currently Teiid Spring Boot only knows of a single translator version. On the other hand one possible solution is to document that by not specifying a url you are at the mercy of Teiid Spring Boot as to which api version it will use. > Document migration for alias names > ---------------------------------- > > Key: TEIIDSB-192 > URL: https://issues.redhat.com/browse/TEIIDSB-192 > Project: Teiid Spring Boot > Issue Type: Task > Components: documentation > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.5.0 > > Original Estimate: 4 hours > Time Spent: 2 hours > Remaining Estimate: 2 hours > > Translators like salesforce and actian-vector has new name in the spring boot, we need to either document or switch back to original names. > Also if we are updating migration utilities we can build in smarts into it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-197) Add a module for each external source

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-197: -------------------------------------- Summary: Add a module for each external source Key: TEIIDSB-197 URL: https://issues.redhat.com/browse/TEIIDSB-197 Project: Teiid Spring Boot Issue Type: Enhancement Reporter: Steven Hawkins Assignee: Ramesh Reddy To simplify the logic in the operator each external source should be represented by a maven artifact - org.teiid:spring-data-x. Any dependency management would be handled in that module and not in the operator - to remove the need for a config file containing driver versions. Additionally property handling should be moved into Teiid Spring Boot such that the operator does not need to know what property prefix is expected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-192) Document migration for alias names

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-192?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIIDSB-192: ----------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours Sprint: DV Sprint 63 > Document migration for alias names > ---------------------------------- > > Key: TEIIDSB-192 > URL: https://issues.redhat.com/browse/TEIIDSB-192 > Project: Teiid Spring Boot > Issue Type: Task > Components: documentation > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.5.0 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Translators like salesforce and actian-vector has new name in the spring boot, we need to either document or switch back to original names. > Also if we are updating migration utilities we can build in smarts into it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-192) Document migration for alias names

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-192?focusedWorklogId=12450970&pa... ] Steven Hawkins logged work on TEIIDSB-192: ------------------------------------------ Author: Steven Hawkins Created on: 05/May/20 9:33 PM Start Date: 05/May/20 9:33 PM Worklog Time Spent: 2 hours Work Description: Logged the related mysql issue and updated the external source names for consistency. Issue Time Tracking ------------------- Remaining Estimate: 2 hours (was: 4 hours) Time Spent: 2 hours Worklog Id: (was: 12450970) > Document migration for alias names > ---------------------------------- > > Key: TEIIDSB-192 > URL: https://issues.redhat.com/browse/TEIIDSB-192 > Project: Teiid Spring Boot > Issue Type: Task > Components: documentation > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.5.0 > > Original Estimate: 4 hours > Time Spent: 2 hours > Remaining Estimate: 2 hours > > Translators like salesforce and actian-vector has new name in the spring boot, we need to either document or switch back to original names. > Also if we are updating migration utilities we can build in smarts into it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-196) Update Spring Boot to Version 2.2.6

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-196?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-196: --------------------------------- Fix Version/s: 1.5.0 > Update Spring Boot to Version 2.2.6 > ----------------------------------- > > Key: TEIIDSB-196 > URL: https://issues.redhat.com/browse/TEIIDSB-196 > Project: Teiid Spring Boot > Issue Type: Task > Components: core > Reporter: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > > Update Spring Boot version to 2.2.6 which is going to be released in support next couple weeks -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5859) Upgrade to wildfly 19

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5859?page=com.atlassian.jira.plugi... ] Work on TEIID-5859 started by Steven Hawkins. --------------------------------------------- > Upgrade to wildfly 19 > --------------------- > > Key: TEIID-5859 > URL: https://issues.redhat.com/browse/TEIID-5859 > Project: Teiid > Issue Type: Task > Components: Build/Kits, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0 > > > We should pick up the latest wildfly 18+ -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-192) Document migration for alias names

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-192?page=com.atlassian.jira.plug... ] Steven Hawkins reassigned TEIIDSB-192: -------------------------------------- Assignee: Steven Hawkins > Document migration for alias names > ---------------------------------- > > Key: TEIIDSB-192 > URL: https://issues.redhat.com/browse/TEIIDSB-192 > Project: Teiid Spring Boot > Issue Type: Task > Components: documentation > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.5.0 > > > Translators like salesforce and actian-vector has new name in the spring boot, we need to either document or switch back to original names. > Also if we are updating migration utilities we can build in smarts into it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-192) Document migration for alias names

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-192?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-192: ---------------------------------------- Other than salesforce, we have: actian-vector actian sqlserver mssql-server sap-iq spaiq I think actian-vector should remain actian-vector - there are other actian database products. Note spaiq is misspelled - for consistency, I think this should also remain sap-iq. I'll add a sqlserver external source that is the same as ms sql server - but that name for consistency should either be ms-sqlserver or ms-sql-server. > Document migration for alias names > ---------------------------------- > > Key: TEIIDSB-192 > URL: https://issues.redhat.com/browse/TEIIDSB-192 > Project: Teiid Spring Boot > Issue Type: Task > Components: documentation > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.5.0 > > > Translators like salesforce and actian-vector has new name in the spring boot, we need to either document or switch back to original names. > Also if we are updating migration utilities we can build in smarts into it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

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

by Manoj Majumdar (Jira)

Manoj Majumdar created TEIID-5949: ------------------------------------- Summary: 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 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, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2020