[
https://issues.apache.org/jira/browse/PHOENIX-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184123#comment-17184123
]
Josh Elser commented on PHOENIX-6074:
-------------------------------------
Restating, you're thinking about adding Phoenix-specific administrative stuff
into PQS?
Being able to report on health via IndexScrutiny sounds reasonable to me. I'm
worried about running IndexTool inside of PQS -- how would we be able to make
sure that IndexTool tasks don't interrupt normal user queries?
I think the idea of this is simple and reasonable. I think the devil is in the
details of how you will implement this, how clients will use it (How is the
REST api defined?), how will you secure it? Lots of open questions :)
> 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)
