[
https://issues.jboss.org/browse/TEIIDDES-3010?page=com.atlassian.jira.plu...
]
Steven Hawkins reassigned TEIIDDES-3010:
----------------------------------------
Description:
TEIID-4627 adds support for source level triggers to be called after CDC events.
The triggers are similar to what is supported by views, but "INSTEAD OF" is not
supported - just AFTER.
CREATE TRIGGER name ON table AFTER (INSERT|UPDATE|DELETE) FOR EACH ROW statement
Just like view triggers new/old/changing values can be referenced. Note that unlike view
triggers, these must be named as an arbitrary number of them are supported per table (like
other of our constructs they are scoped to the table, not to the schema).
We may eventually want to support multiple event types for a single trigger and may need
to support internal events as well.
was:We should look into high-level plugability of event handling at a row level. This
could even be handled at the language level with new trigger semantics for source tables:
create trigger on tbl on cdc (insert|update...) - which could potentially even specify the
topic mapping other details. There is complexity for multi-source models here though.
Assignee: (was: Steven Hawkins)
High-level event handling
-------------------------
Key: TEIIDDES-3010
URL:
https://issues.jboss.org/browse/TEIIDDES-3010
Project: Teiid Designer
Issue Type: Enhancement
Reporter: Steven Hawkins
TEIID-4627 adds support for source level triggers to be called after CDC events.
The triggers are similar to what is supported by views, but "INSTEAD OF" is not
supported - just AFTER.
CREATE TRIGGER name ON table AFTER (INSERT|UPDATE|DELETE) FOR EACH ROW statement
Just like view triggers new/old/changing values can be referenced. Note that unlike view
triggers, these must be named as an arbitrary number of them are supported per table (like
other of our constructs they are scoped to the table, not to the schema).
We may eventually want to support multiple event types for a single trigger and may need
to support internal events as well.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)