Target releaseNice-to-have for DP0.2; needed for DP2 / SV
Epic
Document status
DRAFT
Document owner

Gregory Dubois-Felsmann

Developers
DependenciesCapability already in Qserv
NotesColin to verify that abort passes down correctly to Qserv

Goals

  • Pass the UWS ABORT message 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.

Assumptions

Requirements

#TitleUser StoryImportanceNotes
1
2



User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

Not Doing