[
https://issues.apache.org/jira/browse/PHOENIX-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mehdi Salarkia updated PHOENIX-6074:
------------------------------------
Summary: Let PQS Act As An Admin Tool Rest Endpoint (was: Let PQS Act As
An Admin Tool Endpoint)
> Let PQS Act As An Admin Tool Rest Endpoint
> ------------------------------------------
>
> Key: PHOENIX-6074
> URL: https://issues.apache.org/jira/browse/PHOENIX-6074
> Project: Phoenix
> Issue Type: Improvement
> Components: queryserver
> Reporter: Mehdi Salarkia
> Assignee: Mehdi Salarkia
> Priority: Minor
>
> In our production environment we need to create a lot of indexes and use
> indexTool to build the index also sometime use tools like indexScrutiny to
> verify the health and status of indexes, etc.
> PQS can act as a REST API end point (proxy) that allows developers to call
> and run commands that phoenix currently support via command line only:
> * IndexTool
> * IndexScrutiny
> Benefits:
> # Allow developers to develop tools in their application to run and
> integrate phoenix command line tools into their application without a human
> intervention.
> # Remove unnecessary access permission to production from non admins.
> # Simplify the Index management (or any other future command line tool that
> will be added to phoenix) and remove the possibility of human error, etc.
> I was looking at the implementation PHOENIX-5827 as an example. I think we
> can simply define a new context and use that to trigger phoenix command line
> tools from PQS and return the result (perhaps the MR job link,...) to the
> client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
