[
https://issues.apache.org/jira/browse/IMPALA-12737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836715#comment-17836715
]
Michael Smith commented on IMPALA-12737:
----------------------------------------
A few more questions:
Should {code}select * from table1 join table2 where table1.id = table2.id{code}
list {{table1.id}} and {{table2.id}} in both Where clause and Join clause? Or
just Join clause?
ACID tables have a hidden structure {{row__id}} used for deletes. I think we
can omit that from the Join clause listing.
> Include List of Referenced Columns in Query Log Table
> -----------------------------------------------------
>
> Key: IMPALA-12737
> URL: https://issues.apache.org/jira/browse/IMPALA-12737
> Project: IMPALA
> Issue Type: Bug
> Reporter: Manish Maheshwari
> Assignee: Michael Smith
> Priority: Major
> Labels: workload-management
>
> In the Impala query log table where completed queries are stored, add lists
> of columns that were referenced in the query. The purpose behind this
> functionality is to know which columns are part of
> * Select clause
> * Where clause
> * Join clause
> * Aggegrate clause
> * Order by clause
> There should be a column for each type of clause, so that decisions can be
> made based on specific usage or on the union of those clauses.
> With this information, we will feed into compute stats command to collect
> stats only on the required columns that are using in joins / filters and
> aggegrates and not on all the table columns.
> The information can be collected as an array of
> [db1.table1.column1,db1.table1.column2]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
