[
https://issues.apache.org/jira/browse/PHOENIX-7376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned PHOENIX-7376:
-------------------------------------
Assignee: Viraj Jasani
> ViewUtil#findAllDescendantViews should provide two versions to differentiate
> CQSI initiated by clients and servers
> ------------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-7376
> URL: https://issues.apache.org/jira/browse/PHOENIX-7376
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 5.2.0
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
>
> ViewUtil#findAllDescendantViews provides ability to retrieve all the
> descendant views of a given table or view by scanning the hierarchy of parent
> to child in the depth-first fashion. While this utility was initially built
> for coprocessor endpoints, it creates CQSI connection using with server
> connection property: IS_SERVER_CONNECTION.
> While we don't have server connection specific logic, we need to provide
> separate RPC handler pools for server to server RPC calls for System tables
> (PHOENIX-7370). In order to properly differentiate connections being created
> from client to server vs server to server, ViewUtil#findAllDescendantViews()
> should provide two flavors - one to be used by client to server connections.
> For instance, PHOENIX-7067 and PHOENIX-4555 should use client version of
> ViewUtil#findAllDescendantViews() whereas all MetaDataEndpointImpl should use
> server version of ViewUtil#findAllDescendantViews().
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
