Retrieving query status and cancelling query

[bblodg]

It seems that the kill and query commands call the "v1/query/" endpoint, however I'm getting the following 404 path not found error:
{"timestamp: "...", "status":404, "error": "Not Found", "path":"v1/query/{query-id}"}

I noticed that in Presto + Trino documentation, they say that these get and delete requests should be made to the nextUri, which include the "v1/statement" path as opposed to above: https://prestodb.io/docs/current/develop/client-protocol.html

[MasterOdin]

Looks like doing DELETE /v1/query/{query-id} was the suggested mechanism back in 2019 (https://github.com/prestodb/presto/wiki/HTTP-Protocol), but they've since changed that at some point to instead doing the DELETE against the nextUri.

[brandonw]

I think the issue may lie in that they are used in different contexts.

DELETE /v1/query/<query-id> is an administrative endpoint that requires an authenticated user with permission to terminate arbitrary queries.

DELETE $nextUri is the inline endpoint used to terminate that query (and only that query) and has different authentication requirements (included within the URI, not via header).

In the cases that 404 occur it is probably because the client trying to cancel the query is running the query, so it can do the latter approach. When the former is attempted, it fails because the client doesn't have permission to delete arbitrary queries.

I think that means this client library should only really use the 2nd approach? Or at least, if the first is allowed, it requires a different auth context and is not done inline within a query that is actively executing and is instead only done out-of-band.

[brandonw]

Revising my prior comment for better accuracy: it is not an administrative permissions issue. I believe it is actually specifically for cases where trino has a managed gateway in front of it (in the case I am seeing: https://www.starburst.io/starburst-galaxy/) where that gateway does not support the administrative endpoint to cancel an arbitrary query at all. So the 404 is not a 403 in disguise-- it is literally "this endpoint does not exist".