[
https://issues.apache.org/jira/browse/IMPALA-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16819562#comment-16819562
]
ASF subversion and git services commented on IMPALA-6050:
---------------------------------------------------------
Commit c0a6aad28dd1efaf388f0cfeaa056995213d56e5 in impala's branch
refs/heads/master from Joe McDonnell
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=c0a6aad ]
IMPALA-8415: Fix tests broken by storage layer information
Storage layer information was added to the query profile by
IMPALA-6050. This broke some tests on exhaustive and s3 runs
due to changes in formatting.
This fixes the issues:
1. Replace HDFS SCAN with $FILESYSTEM_NAME SCAN in some test files
2. Add $FILESYSTEM_NAME to partition information string
Testing:
- Ran exhaustive HDFS tests
- Ran s3 tests
Change-Id: I11c6ab9c888464a0f0daaf8a7a6f565d25731872
Reviewed-on: http://gerrit.cloudera.org:8080/13025
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Query profiles should clearly indicate storage layer(s) used
> ------------------------------------------------------------
>
> Key: IMPALA-6050
> URL: https://issues.apache.org/jira/browse/IMPALA-6050
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: Sailesh Mukil
> Assignee: Sahil Takiar
> Priority: Major
> Labels: adls, profile, s3, supportability
> Fix For: Impala 3.3.0
>
>
> Currently, the query profile doesn't have the location of tables and
> partitions, which makes it hard to figure out what storage layer a
> table/partition that was queried was on.
> As we're seeing more users run Impala workloads against cloud based storage
> like S3 and ADLS, we should have the query profiles show this information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
