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

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

Commit e4b349e15a47fc113f20233fed19d2a494f5878c in impala's branch 
refs/heads/master from [~asherman]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=e4b349e ]

IMPALA-7579: fix test_query_profile_contains_all_events on S3

This bug was introduced by IMPALA-6568 which added the
test_query_profile_contains_all_events test. This test creates a file
in the filesystem so that it can be used by 'load data inpath'. The
test was using the hdfs_client object to do file system operations, but
this client only works with hdfs. Switch to using the filesystem_client
object which can work on other filesystems, including s3. Also create
the file that will be moved by 'load data inpath' under the unique
database directory; this means the file can be created without having to
check if it exists already and must be deleted.

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


> The profile of all statements should contain the Query Compilation timeline
> ---------------------------------------------------------------------------
>
>                 Key: IMPALA-6568
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6568
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Frontend
>    Affects Versions: Impala 2.9.0, Impala 2.10.0, Impala 2.11.0
>            Reporter: Alexander Behm
>            Assignee: Andrew Sherman
>            Priority: Major
>              Labels: supportability
>             Fix For: Impala 3.1.0
>
>
> Some statements do not seem to include the "Query Compilation" timeline in 
> the query profile.
> Repro:
> {code}
> create table t (i int);
> describe t; <-- loads the table, but no FE timeline in profile
> invalidate metadata t;
> alter table t set tbproperties('numRows'='10'); <-- loads the table, but no 
> FE timeline in profile
> {code}
> All statements should include the planner timeline.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to