Quarry uses the SHOW EXPLAIN FOR <connection id> method to get the EXPLAINs of queries (ping T50875 T146483)
This method requires the SHOW EXPLAIN FOR being run on the very same host as the one the query is executed, but the analytics cluster is two hosts with a proxy at the front doing round-robin, without a way to force a routing. Therefore SHOW EXPLAIN FOR on a second connection is not very reliable.
What I would like is a reliable method that, given a certain SQL SELECT statement (or preferably allow multiple statements as well, since Quarry allows that), it returns the typical table that EXPLAIN SELECT ... gives.