You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the query plan already does this computation since the other formats expose the columns but hard to parse and varies for connectors.
Example Screenshots (if appropriate):
Context
We are proving audit logs for our customers to find which scientists in their group are querying for sensitive data which are stored at the column level. Based on the column names we would provide logs which then they'd need to submit for compliance.
The text was updated successfully, but these errors were encountered:
When you run a explain query and set type to IO, it returns the input tables, but doesn't return the columns used per table.
Expected Behavior or Use Case
You get the following result:
The expected result:
Presto Component, Service, or Connector
query plan
Possible Implementation
I think the query plan already does this computation since the other formats expose the columns but hard to parse and varies for connectors.
Example Screenshots (if appropriate):
Context
We are proving audit logs for our customers to find which scientists in their group are querying for sensitive data which are stored at the column level. Based on the column names we would provide logs which then they'd need to submit for compliance.
The text was updated successfully, but these errors were encountered: