Belén Pruvost

> Maybe instead of adding a new endpoint we should add a query parameter to the existing endpoint? > > `/v1/query/{queryId}?pruned=true` Definitely sounds like a good idea 👍 I'll update...

@wendigo I've incorporated your feedback and sent the CLA via email, so this PR should be good for another review, when you have the time 🙏

> One question: how do you plan to consume this endpoint? There is no usage of it so far in the Trino's codebase. We're calling it from a separate client...

> @belen-pruvost , we recently merged #21075 . Please check whether it resolve your problem. Thanks for the pointer - I'll give it a try and report back here if...

I've pushed the changes with the comments here addressed. I still need to test if using `getResultQueryInfo` instead of `pruneQueryInfo` would achieve something similar.

Unfortunately relying on `BasicQueryInfo` (implemented on https://github.com/trinodb/trino/pull/21075/) won't work for us because the data we need are `referencedTables` and `routines`

> I think we should have usage of this endpoint in Trino web ui or CLI or jdbc client to justify adding it to Trino server. Without seeing how it...

> I don't have any particular usage in mind, may be think about how you intended to use it and see if that can fit somewhere in Trino web UI....

> Why would anyone want to see "pruned JSON" in the UI if they can see normal JSON there? It does not add any value, I'll remove it and use...

I ended up following @mosabua's suggestion and implemented an additional view called `References`, which shows Referenced Tables and Routines by making used of the pruned parameter. A few screenshots of...