[
https://issues.jboss.org/browse/TEIID-4641?page=com.atlassian.jira.plugin...
]
Ramesh Reddy resolved TEIID-4641.
---------------------------------
Resolution: Done
Labels: Beta1 (was: )
Modified load/refresh strategy to use UPSERT/DELETE rather than the INSERT/DELETE from
before. The process is documented with this commit [1]. Note, that this process is much
more simpler and does not require a staging table nor defining the load scripts. The
previous behavior based on staging table, and load scripts still exists for backwards
compatibility, it just not documented any more.
[1]
https://github.com/teiid/teiid-documents/commit/c30b2ad19e2b5ed9fdc13ee39...
Create upsert/delete refresh support
------------------------------------
Key: TEIID-4641
URL:
https://issues.jboss.org/browse/TEIID-4641
Project: Teiid
Issue Type: Sub-task
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Labels: Beta1
Fix For: 9.2
There must be an alternative to the implied default of the table rename strategy - which
is problematic when a source is not transactional or even when it is - as a multi-part
swap can leave the table non-existent for a brief window or the source may have issues
with ddl under an xa transaction - TEIID-4579
This is true for the non-transactional source incremental refresh as well, which is a
delete then insert - it leaves the live table briefly in an inconsistent state.
A upsert/delete approach addresses both of these concerns at the expense of performance -
especially when the source does not directly support upsert as the engine must implement a
compensating procedure. However now that we have pushdown support for upsert, we'll
continue to add source support.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)