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

[Steven Hawkins (JIRA)]

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

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

Refinements that will be needed:

The old trigger logic assumes (like other databases) that views can only have 1 instead of trigger for each event type.  This lead to us defining the trigger handling without an explicit name.  Adding name handling will cause an issue with the event distributor logic (at the least new methods).  A simpler approach will be to just not allow issuing a runtime create/alter for a source trigger.  This also will imply that an explicit drop trigger, or enabled handling similar to the virtual layer, will not yet be needed either.  Then we can work through the runtime issues in TEIID-2578

I'll need to separate out both a create and an alter trigger command statement to keep the logic cleaner.

The old trigger handling also did not treat the view triggers as first class entities (either at the schema level or as children of the table).  Adding uids, allowing annotations, etc. and corresponding wiring in the system tables is all possible, but won't work for the view  layer unless they are converted to proper objects as well.

> High-level event handling
> -------------------------
>
>                 Key: TEIID-4627
>                 URL: https://issues.jboss.org/browse/TEIID-4627
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: Grammar, 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)