[
https://issues.apache.org/jira/browse/IMPALA-14138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18008251#comment-18008251
]
ASF subversion and git services commented on IMPALA-14138:
----------------------------------------------------------
Commit d5f7cc3a0b39e106ef7c090338e5ab1afdef8617 in impala's branch
refs/heads/master from Zoltan Borok-Nagy
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=d5f7cc3a0 ]
IMPALA-14138: Addendum test fix
This patch moves out a query from no-block-locations.test to only run
it on HDFS because the queried Iceberg table has Iceberg delete files
that contain HDFS-specific URIs.
Change-Id: Iea862dd3b73a9aceceeb848d0ac85ac87627c8c2
Reviewed-on: http://gerrit.cloudera.org:8080/23189
Reviewed-by: Daniel Becker <[email protected]>
Reviewed-by: Csaba Ringhofer <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Detect if filesystem is not co-located in which case we shouldn't collect
> block location information
> ----------------------------------------------------------------------------------------------------
>
> Key: IMPALA-14138
> URL: https://issues.apache.org/jira/browse/IMPALA-14138
> Project: IMPALA
> Issue Type: Bug
> Reporter: Zoltán Borók-Nagy
> Priority: Major
> Labels: impala-iceberg
>
> For storage systems that support block location information (HDFS, Ozone) we
> always retrieve it with the assumption that we can use it for scheduling, to
> do local reads:
> [https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/catalog/IcebergFileMetadataLoader.java#L154]
> But it's also typical that Impala is not co-located with the storage system,
> not even in on-prem deployments. E.g. PVC DS Impala runs in containers, and
> even if they are co-located, I don't think we try to figure out which
> container runs on which machine. Also short-circuit reads are off the
> table.In such cases we should not reach out to the storage system to collect
> file information because it can be very expensive for large tables and we
> won't benefit from it at all.
>
> We could construct the file descriptors based on the information we have in
> the Iceberg manifests, and this is what we already do on cloud storage
> systems.
> Is there a good indicator that Impala is not co-located with the configured
> filesystems? E.g. if data cache is enabled? But of course there could be
> multiple filesystems configured, some of them co-located, some not..
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
