Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-6074

Let PQS Act As An Admin Tool Rest Endpoint

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: queryserver
    • Labels:
      None

      Description

      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:

      1. Allow developers to develop tools in their application to run and integrate phoenix command line tools into their application without a human intervention.
      2. Remove unnecessary access permission to production from non admins.
      3. 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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                m2je Mehdi Salarkia
                Reporter:
                m2je Mehdi Salarkia
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: