[ 
https://issues.apache.org/jira/browse/PHOENIX-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16910766#comment-16910766
 ] 

Geoffrey Jacoby edited comment on PHOENIX-5449 at 8/19/19 9:47 PM:
-------------------------------------------------------------------

We may actually want two consumers, one that just rehydrates the fields that 
were edited, and another that does the same but also supplements the edited 
fields by SELECTing the unedited fields back out of Phoenix at the appropriate 
SCN. Clients could choose which ones to use. Alternately, it could be one 
consumer with a config switch. 


was (Author: gjacoby):
We may actually want two consumers, one that just rehydrates the fields that 
were edited, and another that supplements the edited fields by SELECTing the 
unedited fields back out of Phoenix at the appropriate SCN. Clients could 
choose which ones to use. Alternately, it could be one consumer with a config 
switch. 

> Schema-aware Message Consumer
> -----------------------------
>
>                 Key: PHOENIX-5449
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5449
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Geoffrey Jacoby
>            Assignee: Geoffrey Jacoby
>            Priority: Major
>
> The change data capture ReplicationEndpoint will be persisting data to the 
> message bus using a low-level, generic schema that includes a pointer to 
> schema information, plus a list of Cells (like an Avro-encoded WAL Entry). 
> This is done both because some low-level use cases such as backup don't the 
> strong typing until restore-time, but also to simplify the endpoint and 
> improve performance. The endpoint will be decoupled from any consumer that 
> wants to do higher level processing on any entity type. 
> There will be a need, however, for a message bus consumer that reads in the 
> low-level messages from the ReplicationEndpoint, looks up the schema using 
> the metadata in the message and the API in PHOENIX-5443, and then 
> "rehydrates" the low-level message into a higher-level, strongly-typed 
> message suitable for running business logic on. 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to