- Pass the UWS
ABORTmessage through to Qserv.
Background and strategic fit
Allows users to abandon queries which were launched in error or without understanding that they would trigger a lengthy table scan.
Qserv already provides a query-cancellation capability:
- For "disconnected" queries, for which for the client (i.e., the TAP service) has received an ID, there is a Qserv interface for cancellation by ID.
- For "connected" queries (which the Rubin TAP service is currently using even for asynchronous TAP queries) simply dropping the connection triggers Qserv to cancel the query.
User interaction and design
Below is a list of questions to be addressed as a result of this requirements document: