[
https://issues.jboss.org/browse/TEIID-4627?page=com.atlassian.jira.plugin...
]
Ramesh Reddy edited comment on TEIID-4627 at 1/20/17 5:53 PM:
--------------------------------------------------------------
[~shawkins] I see that in the initial commit, there is no handling for OLD values in the
{{SourceTriggerActionPlanner.java}} can you please add that support?
Also, for "Insert" case, I see that SourceEventCommand never finishes and keeps
looping in QueryProcessor.nextBatchDirect() method, thus running the CPU cycles high. I
think it does not have terminate flag on tuples as last batch.
was (Author: rareddy):
[~shawkins] I see that in the initial commit, there is no handling for OLD values in the
{{SourceTriggerActionPlanner.java}} can you please add that support?
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)