[ 
https://issues.apache.org/jira/browse/IMPALA-12737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896398#comment-17896398
 ] 

ASF subversion and git services commented on IMPALA-12737:
----------------------------------------------------------

Commit a46625a3c03a50275cdf91d3abc2f8e445913c2b in impala's branch 
refs/heads/master from Jason Fehr
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=a46625a3c ]

IMPALA-12737: (addendum) Turn Off Log Buffering in Workload Management Init 
Tests

Fixes the issue where custom cluster workload management tests do not
disable glog log buffering in tests that wait for specific messages
to be logged from the coordinators and catalogs.

By default, logs are buffered up to 30 seconds. This buffering can
cause unnecessary test slowness while the tests wait longer than
needed for the expected log message to be flushed and can also cause
flakiness where the tests do not find the expected log message before
the timeout expires.

Change-Id: I03ac0f0f00c93fe785db131278a706e3f5e975c2
Reviewed-on: http://gerrit.cloudera.org:8080/22021
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> 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: Improvement
>            Reporter: Manish Maheshwari
>            Assignee: Jason Fehr
>            Priority: Critical
>              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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to