[JBoss JIRA] (TEIID-3907) Support compensating transactions for updatable non-XA sources
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3907?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3907:
---------------------------------------
We will look at this again for 11.0 using row by row compensating procedures rather than relying on changes at the resource adapter level.
> Support compensating transactions for updatable non-XA sources
> --------------------------------------------------------------
>
> Key: TEIID-3907
> URL: https://issues.jboss.org/browse/TEIID-3907
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 9.x
> Reporter: Van Halbert
> Fix For: 11.0
>
>
> The transaction manager will fully support xa with all xa sources and a single local transaction resource. Beyond that however there is no built-in support for compensating transactions with non-XA sources. There has been work in Narayana on compensating transactions though that could be used by custom web apps consuming Teiid. We would like to eventually offer compensating options for some of our updatable non-XA sources, but it hasn't had sufficient priority yet.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-3907) Support compensating transactions for updatable non-XA sources
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3907?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-3907:
-------------------------------------
Assignee: Steven Hawkins
> Support compensating transactions for updatable non-XA sources
> --------------------------------------------------------------
>
> Key: TEIID-3907
> URL: https://issues.jboss.org/browse/TEIID-3907
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 9.x
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 11.0
>
>
> The transaction manager will fully support xa with all xa sources and a single local transaction resource. Beyond that however there is no built-in support for compensating transactions with non-XA sources. There has been work in Narayana on compensating transactions though that could be used by custom web apps consuming Teiid. We would like to eventually offer compensating options for some of our updatable non-XA sources, but it hasn't had sufficient priority yet.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-3907) Support compensating transactions for updatable non-XA sources
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3907?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3907:
----------------------------------
Fix Version/s: 11.0
(was: 11.x)
> Support compensating transactions for updatable non-XA sources
> --------------------------------------------------------------
>
> Key: TEIID-3907
> URL: https://issues.jboss.org/browse/TEIID-3907
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 9.x
> Reporter: Van Halbert
> Fix For: 11.0
>
>
> The transaction manager will fully support xa with all xa sources and a single local transaction resource. Beyond that however there is no built-in support for compensating transactions with non-XA sources. There has been work in Narayana on compensating transactions though that could be used by custom web apps consuming Teiid. We would like to eventually offer compensating options for some of our updatable non-XA sources, but it hasn't had sufficient priority yet.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-587) Better pushdown support for exotic joins
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-587?page=com.atlassian.jira.plugin.... ]
Steven Hawkins resolved TEIID-587.
----------------------------------
Resolution: Out of Date
Marking as out of date. The specific salesforce issues listed above have been worked around. The remaining central salesforce issue is that we limit pushdown to a single join - but that is more of a translator limitation than an engine issue at this point. There is also TEIID-3531 that serves as a general join planning issue.
> Better pushdown support for exotic joins
> ----------------------------------------
>
> Key: TEIID-587
> URL: https://issues.jboss.org/browse/TEIID-587
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 6.1.0
> Reporter: Steven Hawkins
> Fix For: 11.x
>
>
> Our optimizations get in the way of Salesforce pushdown. Specifically rewriting like when possible to = and converting outer joins to inner joins. In both cases we would need to not perform the optimization in the first place or convert into an acceptable form prior to pushdown.
> The next is that salesforce, while requiring key criteria also allows other criteria in the left outer join on clause (which would be the same as having criteria on the nested relationship query in the salesforce query). With the capabilities as currently defined this would cause the query to not be pushed down. We should consider adding a relational supported join criteria type that requires key criteria but allows for outside criteria. Also we should treat the lack of inner join support to mean that criteria on the inner side of an outer join cannot be pushed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-587) Better pushdown support for exotic joins
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-587?page=com.atlassian.jira.plugin.... ]
Steven Hawkins updated TEIID-587:
---------------------------------
Fix Version/s: (was: 11.x)
> Better pushdown support for exotic joins
> ----------------------------------------
>
> Key: TEIID-587
> URL: https://issues.jboss.org/browse/TEIID-587
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 6.1.0
> Reporter: Steven Hawkins
>
> Our optimizations get in the way of Salesforce pushdown. Specifically rewriting like when possible to = and converting outer joins to inner joins. In both cases we would need to not perform the optimization in the first place or convert into an acceptable form prior to pushdown.
> The next is that salesforce, while requiring key criteria also allows other criteria in the left outer join on clause (which would be the same as having criteria on the nested relationship query in the salesforce query). With the capabilities as currently defined this would cause the query to not be pushed down. We should consider adding a relational supported join criteria type that requires key criteria but allows for outside criteria. Also we should treat the lack of inner join support to mean that criteria on the inner side of an outer join cannot be pushed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5135) REPEAT function truncates strings to 4000 characters
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5135?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5135.
-----------------------------------
Resolution: Done
Marking as resolved by adding a truncation warning anytime a string is truncated.
> REPEAT function truncates strings to 4000 characters
> ----------------------------------------------------
>
> Key: TEIID-5135
> URL: https://issues.jboss.org/browse/TEIID-5135
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Affects Versions: 9.3.4
> Environment: teiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 11.0
>
>
> Probably it's not bug. When running the following queries:
> {code:sql}
> Select Length(Repeat('abcde', 9000));; /* 4000 chars */
> Select Length(Repeat('a', 9000));; /* 4000 chars */
> {code}
> Teiid returns 4000 instead of 9000. Can the internal truncation be avoided (maybe in some cases) or not?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5285) Add high-level feature for redirection of updates
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin... ]
Ramesh Reddy reassigned TEIID-5285:
-----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> Add high-level feature for redirection of updates
> -------------------------------------------------
>
> Key: TEIID-5285
> URL: https://issues.jboss.org/browse/TEIID-5285
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine, Teiid Spring Boot
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 11.x
>
>
> In microservices testing it is desirable to test against production/live data but not commit any updates. We should offer a simple solution that can defined by extension metadata and enabled/disabled by a feature flag. We may need to make simplifying assumptions about the scope (per session, per application, etc.) and durability of the updates.
> Under the covers this will be achieved by using views, update triggers, and a store for the updates and when not enabled the expectation is that all operations should pass through. However the application will be limited to using Teiid SQL and will be required to use the Teiid or pg driver, or Teiid spring boot.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (TEIID-5369) enableDependentJoins for Redshift translator
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5369?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5369.
-----------------------------------
Fix Version/s: 10.3.2
Resolution: Done
Added an override to omit the on commit clause.
> enableDependentJoins for Redshift translator
> --------------------------------------------
>
> Key: TEIID-5369
> URL: https://issues.jboss.org/browse/TEIID-5369
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Connector
> Reporter: Chandra Akkinepalli
> Assignee: Steven Hawkins
> Fix For: 11.0, 10.3.2
>
>
> When using Translator overwrite property enableDependentJoins with Redshift translator, we got the following error.
> Caused by: java.sql.SQLException: [Amazon](500310) Invalid operation: CREATE TEMP TABLE ON COMMIT is not supported; at com.amazon.redshift.client.messages.inbound.ErrorResponse.toErrorException(ErrorResponse.java:1830) ... 30 lines omitted ... at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) Caused by: com.amazon.support.exceptions.ErrorException: [Amazon](500310) Invalid operation: CREATE TEMP TABLE ON COMMIT is not supported; ... 32 more
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months