[JBoss JIRA] (TEIID-3546) Add distinct from syntax in for each row procedures
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3546:
-------------------------------------
Summary: Add distinct from syntax in for each row procedures
Key: TEIID-3546
URL: https://issues.jboss.org/browse/TEIID-3546
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 8.12
Similar to postgresql, it would be good to allow for a quick comparison of new/old values to determine if row processing is needed. Something like:
IF new IS DISTINCT FROM old THEN
...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3545) Improvements in default handling
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3545:
-------------------------------------
Summary: Improvements in default handling
Key: TEIID-3545
URL: https://issues.jboss.org/browse/TEIID-3545
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.12
The current default field is just a string value and captured as a string value at import time - in general it should be allowed to be an expression. Also our insert syntax should support the default/defaults keywords and be able to propagate that to the source, rather than using the default on the model.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3534) Infinispan-dsl-cache translator: can't insert null into column of type boolean
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3534?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3534:
---------------------------------------
The first two inserts are likely the same if the column is marked as nullable. It seems surprising that a null boolean value is not allowed though, can you check if that is expected? Does this happen if other values are null?
If null is not allowed, then the column should be marked as not null. The if no default is specified, an exception will be thrown saying a value is required. Or if there is a default, it will be used.
> Infinispan-dsl-cache translator: can't insert null into column of type boolean
> ------------------------------------------------------------------------------
>
> Key: TEIID-3534
> URL: https://issues.jboss.org/browse/TEIID-3534
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7.1.6_2
> Reporter: Filip Elias
> Assignee: Van Halbert
> Attachments: server.log, testVDB.vdb
>
>
> Inserting null into boolean column causes exception.
> Sample queries:
> {code}
> insert into smalla(intKey, stringKey,booleanValue) values(128,'ss',null);
> insert into smalla(intKey, stringKey) values(128,'ss');
> {code}
> This query works:
> {code}
> insert into smalla(intKey, stringKey,booleanValue) values(128,'ss',false);
> {code}
> Exception:
> {code}
> Connector worker process failed for atomic-request=NuZ8Nt3h1bKx.52.0.44: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message id[239] returned server error (status=0x85): org.hibernate.search.bridge.BridgeException: Exception while calling bridge#set
> class: org.infinispan.query.remote.indexing.ProtobufValueWrapper
> path:
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:298)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:88)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:74)
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56)
> {code}
> This bug breaks data integrity. If this exception is thrown, data will be inserted but it won't be indexed.
> The whole exception is in the attachment.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3541) Remove the Teiid embedded kit
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3541?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3541:
----------------------------------
Fix Version/s: 8.12
(was: 8.11)
> Remove the Teiid embedded kit
> -----------------------------
>
> Key: TEIID-3541
> URL: https://issues.jboss.org/browse/TEIID-3541
> Project: Teiid
> Issue Type: Task
> Components: Embedded
> Reporter: Ramesh Reddy
> Assignee: Kylin Soong
> Fix For: 8.12
>
>
> There is no reason to keep a separate embedded kit supplied by Teiid. The scripts that are building the kit needs to be removed from build.
> All the required jar files for the "embedded" examples will be available from the "teiid-embedded-examples". Here we need to focus on documentation, but that is separate effort
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3351) Quick Start "dynamicvdb-datafederation" needlessly made complicated
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3351?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3351:
----------------------------------
Fix Version/s: 8.12
(was: 8.11)
> Quick Start "dynamicvdb-datafederation" needlessly made complicated
> -------------------------------------------------------------------
>
> Key: TEIID-3351
> URL: https://issues.jboss.org/browse/TEIID-3351
> Project: Teiid
> Issue Type: Quality Risk
> Components: Quick Starts
> Reporter: Ramesh Reddy
> Assignee: Van Halbert
> Fix For: 8.12
>
>
> The "dynamicvdb-datafederation" example in the Quick Starts example is needlessly made complicated. Originally this is designed to have one File and RDBMS source, to show a simple data integration through Teiid.
> Now, it has
> - Excel integration
> - Materialization Example
> - more models
> I am not opposed to having these features shown in an example, however not in this example. This needs to be as simple as possible to show a quick introduction to the Teiid. Please move these into separate quick starts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3361) Add source query details to the command log
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3361?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3361:
----------------------------------
Fix Version/s: 8.12
(was: 8.11)
> Add source query details to the command log
> -------------------------------------------
>
> Key: TEIID-3361
> URL: https://issues.jboss.org/browse/TEIID-3361
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.12
>
>
> The command log for convenience only contains the Teiid sql form of the source query. It would be good to have the translators also add their actual form of the source query when possible to the command log just to have a single place to track things down.
> Currently this info is logged to the CONNECTOR context inconsistently in each translator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months