July 2020 - teiid-issues - Jboss List Archives

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

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5950?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5950: ---------------------------------- Sprint: DV Sprint 66 > 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 > Priority: Major > Fix For: 15.0 > > Original Estimate: 4 hours > Time Spent: 2 hours > Remaining Estimate: 2 hours > > There have been several issues seen with athena using the jdbc ansi translator - subquery support and bind variables specifically. There should be a specific translator so that we can account for those better. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 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)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5981) Add content length to VirtualFileConnection.add

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5981?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5981. ----------------------------------- Resolution: Done Added a filemetadata object to the add method. It will be considered optional and only contains the size information. The size is only used by s3 for now. > Add content length to VirtualFileConnection.add > ----------------------------------------------- > > Key: TEIID-5981 > URL: https://issues.redhat.com/browse/TEIID-5981 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 3 hours > Time Spent: 3 hours > Remaining Estimate: 0 minutes > > Using either an InputStreamFactory or another parameter the add method should have the stream length available or -1 if unknown. This will help with protocols that require the length which may otherwise have to materialize the stream in memory or disk to determine the length. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5981) Add content length to VirtualFileConnection.add

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5981?focusedWorklogId=12451824&pag... ] Steven Hawkins logged work on TEIID-5981: ----------------------------------------- Author: Steven Hawkins Created on: 28/Jul/20 1:49 PM Start Date: 28/Jul/20 1:49 PM Worklog Time Spent: 3 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 3 hours) Time Spent: 3 hours Worklog Id: (was: 12451824) > Add content length to VirtualFileConnection.add > ----------------------------------------------- > > Key: TEIID-5981 > URL: https://issues.redhat.com/browse/TEIID-5981 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 3 hours > Time Spent: 3 hours > Remaining Estimate: 0 minutes > > Using either an InputStreamFactory or another parameter the add method should have the stream length available or -1 if unknown. This will help with protocols that require the length which may otherwise have to materialize the stream in memory or disk to determine the length. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5981) Add content length to VirtualFileConnection.add

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5981?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5981: ---------------------------------- Original Estimate: 3 hours Remaining Estimate: 3 hours Sprint: DV Sprint 66 > Add content length to VirtualFileConnection.add > ----------------------------------------------- > > Key: TEIID-5981 > URL: https://issues.redhat.com/browse/TEIID-5981 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > Using either an InputStreamFactory or another parameter the add method should have the stream length available or -1 if unknown. This will help with protocols that require the length which may otherwise have to materialize the stream in memory or disk to determine the length. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 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... ] Work on TEIID-5949 started by Steven Hawkins. --------------------------------------------- > 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 > > > 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)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5981) Add content length to VirtualFileConnection.add

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5981?page=com.atlassian.jira.plugi... ] Work on TEIID-5981 started by Steven Hawkins. --------------------------------------------- > Add content length to VirtualFileConnection.add > ----------------------------------------------- > > Key: TEIID-5981 > URL: https://issues.redhat.com/browse/TEIID-5981 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > > Using either an InputStreamFactory or another parameter the add method should have the stream length available or -1 if unknown. This will help with protocols that require the length which may otherwise have to materialize the stream in memory or disk to determine the length. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5977) There should be a way to push down a virtual function defined in ddl

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5977?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5977. ----------------------------------- Resolution: Done Committed the pr and the associated doc update. For consistency with other similar properties I use "teiid_rel:virtual-function" instead. > There should be a way to push down a virtual function defined in ddl > -------------------------------------------------------------------- > > Key: TEIID-5977 > URL: https://issues.redhat.com/browse/TEIID-5977 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 6 hours > Time Spent: 6 hours > Remaining Estimate: 0 minutes > > If you create a function that is defined in ddl, it currently requires that a translator be extended to add a pushdown function and handling. It would be better if there were a way to do this entirely in ddl. This could be either/or: > 1. when the function is defined by an expression rather than a more complex procedure statement, we should check to see if that can be inlined. > 2. provide a way to match source functions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-6001) OData visible metadata can lead to npe building metadata

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-6001?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-6001. ----------------------------------- Resolution: Done Added more checks to ensure both ends of the navigation exist in the odata metadata. > OData visible metadata can lead to npe building metadata > -------------------------------------------------------- > > Key: TEIID-6001 > URL: https://issues.redhat.com/browse/TEIID-6001 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0, 14.0.1 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > In looking at TEIID-5873 I could see that we weren't checking for visibility when building navigations. So if an entity is not visible, but is on the other side of a foreign key from an entity that is, we'll throw an npe rather than simply not adding the navigations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-6001) OData visible metadata can lead to npe building metadata

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-6001?focusedWorklogId=12451821&pag... ] Steven Hawkins logged work on TEIID-6001: ----------------------------------------- Author: Steven Hawkins Created on: 28/Jul/20 7:56 AM Start Date: 28/Jul/20 7:56 AM Worklog Time Spent: 2 hours, 30 minutes Issue Time Tracking ------------------- Remaining Estimate: 30 minutes (was: 3 hours) Time Spent: 2 hours, 30 minutes Worklog Id: (was: 12451821) > OData visible metadata can lead to npe building metadata > -------------------------------------------------------- > > Key: TEIID-6001 > URL: https://issues.redhat.com/browse/TEIID-6001 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0, 14.0.1 > > Original Estimate: 3 hours > Time Spent: 2 hours, 30 minutes > Remaining Estimate: 30 minutes > > In looking at TEIID-5873 I could see that we weren't checking for visibility when building navigations. So if an entity is not visible, but is on the other side of a foreign key from an entity that is, we'll throw an npe rather than simply not adding the navigations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 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