[ https://issues.jboss.org/browse/TEIID-4526?page=com.atlassian.jira.plugin... ] Randall Hauch commented on TEIID-4526: -------------------------------------- {quote} Our problems with CDC starts with the metadata. Since we allow for hand editing and only capture a simple quoted name in source, we first have a matching problem from any event source to our source metadata. {quote} We're soon going to be adding the database name and table name in the {{source}} structure in each event, and hopefully this will make it a bit easier than inferring the source table name from other information. It may still be somewhat difficult depending upon what's in the Teiid metadata. {quote} * There can be type issues or even the consideration for masking or other effects. Inferring values directly from the change event can be an issue as the CDC layer is broadcasting raw values, not what you would fetch over jdbc. {quote} Yes, Debezium is limited in the way values can be represented, so values will have to be converted. We have a goal that the different connectors use a consistent type mapping, but that won't eliminate the complexity here. One other point. I've suggested that whoever's working on this first try [embedding connectors|http://debezium.io/docs/embedded/]. It eliminates lots of complexities in infrastructure (e.g., Kafka, connections, topic mappings, etc.) so that you can start out focusing on the basics of dealing with events. -- This message was sent by Atlassian JIRA (v7.2.2#72004)