[
https://issues.apache.org/jira/browse/PHOENIX-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752238#comment-17752238
]
Istvan Toth edited comment on PHOENIX-6988 at 8/9/23 3:32 AM:
--------------------------------------------------------------
Are we planning to add observer hooks here ?
If not, then calling it PhoenixRegionServerEndpoint would make more sense, to
distinguish it from all the Observers that we are running on RSs.
was (Author: stoty):
Are we planning to add observer hooks here ?
If not, then calling it PhoenixRegionServerEndpint would make more sense, to
distinguish it from all the Observers that we are running on RSs.
> Create new regionserver coprocessor named PhoenixRegionServerCoprocessor in
> Phoenix
> -----------------------------------------------------------------------------------
>
> Key: PHOENIX-6988
> URL: https://issues.apache.org/jira/browse/PHOENIX-6988
> Project: Phoenix
> Issue Type: Sub-task
> Components: core
> Reporter: Rushabh Shah
> Assignee: Rushabh Shah
> Priority: Major
>
> -Rename ReplicationSinkEndpoint to PhoenixRegionServerCoprocessor so that we
> can add all the phoenix regionserver co-proc methods in just 1 class.-
> Earlier I thought to rename ReplicationSinkCompatEndpoint to
> PhoenixRegionServerCoprocessor but then looking at the code, there are some
> complexities. ReplicationSinkEndpoint extends ReplicationSinkCompatEndpoint
> which is defined in hbase-compat module and it is implemented in different
> hbase-compat modules. The new co-proc is phoenix native co-proc and don't
> need any compatibility guarantees. So I created a new regionserver coproc in
> phoenix-core module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
