Question: a proper way to print a plan after a query finished #15319
Unanswered
agoncharuk
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Trino community,
I am trying to print a JSON logical plan for a query that has already terminated using
PlanPrinter
by pulling the plan fromQueryManager
. The conversion fails becauseTableInfoSupplier
pulls table schema throughMetadataManager
, which in turn callsTransactionManager#getCatalogMetadata(...)
which fails to find transaction metadata because transaction no longer exists.The relevant part of the exception trace:
Is there a proper way to print the JSON plan after the transaction terminated by having only an instance of
Plan
pulled from the query manager? At the first glance, all necessary information should be available in theTableScanNode
itself (however hidden by connector interfaces).Beta Was this translation helpful? Give feedback.
All reactions