[teiid-issues] [JBoss JIRA] (TEIID-4627) High-level event handling

Steven Hawkins (JIRA) issues at jboss.org
Tue Dec 6 16:35:00 EST 2016


    [ https://issues.jboss.org/browse/TEIID-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13334926#comment-13334926 ] 

Steven Hawkins commented on TEIID-4627:
---------------------------------------

On a source table, the event handling could look like:

CREATE TRIGGER name AFTER {event [ OR ... ]} ON table
FOR EACH {ROW | STATEMENT}
BEGIN
  ...
END

For compatibility with our current trigger feature, we could limit to a single event type and FOR EACH ROW.  We may also need to differentiate between locally generated events (an insert through teiid for example) vs. change events supplied to us as to not double process events.




> High-level event handling
> -------------------------
>
>                 Key: TEIID-4627
>                 URL: https://issues.jboss.org/browse/TEIID-4627
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: Query Engine
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 9.2
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the teiid-issues mailing list