[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:
----------------------------------
Story Points: 0.1
Sprint: DV Sprint 63
> 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
>
> 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, 7 months
[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 resolved TEIID-5928.
-----------------------------------
Resolution: Incomplete Description
Resolving as incomplete description, but this also is possibly explained.
> 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
>
> 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, 7 months
[JBoss JIRA] (TEIID-5944) Infinispan protobuf generation fails to validate name with "-" in them
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIID-5944?page=com.atlassian.jira.plugi... ]
Ramesh Reddy commented on TEIID-5944:
-------------------------------------
[~shawkins] protobuf itself does not allow the hyphens in message names, so the calling process needs to make sure it does not provide an invalid name for this, how the name is changed is up to the calling process not run into an issue. Originally I thought Teiid is not generating in correct formats
> Infinispan protobuf generation fails to validate name with "-" in them
> ----------------------------------------------------------------------
>
> Key: TEIID-5944
> URL: https://issues.redhat.com/browse/TEIID-5944
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Priority: Major
>
> When the name of the view contains like "mat-example_vix" the protobuf generation seems to succeed however the validation of it by the Infinispan seems to fail.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[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 commented on TEIID-5949:
---------------------------------------
> Also the datetimeoffset datatype is read as "object(34)" while fetching the schema using Teiid and Microsoft JDBC driver.
For now the workaround would be to alter the source metadata so that it's a Teiid timestamp type.
The bigger fix is to update the translator to assign a better type on import.
> 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: 14.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, 7 months
[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:
----------------------------------
Fix Version/s: 14.1
> 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: 14.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, 7 months