[JBoss JIRA] (TEIID-3360) Provide an option to virtualize source exceptions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3360?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3360:
----------------------------------
Fix Version/s: 9.2
(was: 9.1)
> Provide an option to virtualize source exceptions
> -------------------------------------------------
>
> Key: TEIID-3360
> URL: https://issues.jboss.org/browse/TEIID-3360
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.2
>
>
> Currently we'll pass the source exception along with the Teiid exception. And from source sql exceptions we'll also rely the sql state/code. When connecting to databases of different types it would be best to return a common set of codes.
> There is exception mapping logic in Hibernate that we could reuse, but this could apply to the non-jdbc sources such that a predictable code will seen by Teiid clients.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years
[JBoss JIRA] (TEIID-4456) Enable the abiltiy to support nested and non-nested message descriptors
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4456?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4456.
-----------------------------------
Resolution: Done
Merged the pull request.
> Enable the abiltiy to support nested and non-nested message descriptors
> -----------------------------------------------------------------------
>
> Key: TEIID-4456
> URL: https://issues.jboss.org/browse/TEIID-4456
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Van Halbert
> Assignee: Van Halbert
> Fix For: 9.1
>
>
> Protobuf definition files can have messages defined in a nested and non-nested form.
> Nested:
> {code}
> package bigdata;
> message DataEntity {
> ..
> optional MetaData context = 6;
> message MetaData {
> ...
> }
> }
> {code}
> Non-nested:
> {code}
> package bigdata;
> message DataEntity {
> ..
> optional MetaData context = 6;
> }
> message MetaData {
> ...
> }
> {code}
> The ProtobufMetadataProcessor needs to be changed to so that it can create the metadata from either use case.
> Currently it obtains the child descriptor messages from the parent descriptor.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years
[JBoss JIRA] (TEIID-4481) Support for the upsert statement which is provided by Salesforce API
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4481?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-4481:
-------------------------------------
Component/s: (was: VDB)
Fix Version/s: 9.2
(was: 9.1)
Assignee: (was: Steven Hawkins)
Moving to 9.2. With TEIID-4481 committed it is possible to update both the translator and the resource adapter to handle the pushdown of an insert marked as an upsert.
> Support for the upsert statement which is provided by Salesforce API
> --------------------------------------------------------------------
>
> Key: TEIID-4481
> URL: https://issues.jboss.org/browse/TEIID-4481
> Project: Teiid
> Issue Type: Sub-task
> Components: Connector API, Query Engine, Salesforce Connector
> Reporter: Thomas Esche
> Fix For: 9.2
>
>
> The Salesforce API provides a "upsert" statement, which combines insert and update functionality.
> It would be great to use these feature either by using
> - the connector directly or
> - the UDF's or
> - per SQL.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years