You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Michael Smith (Jira)" <ji...@apache.org> on 2022/09/07 17:55:00 UTC
[jira] [Resolved] (IMPALA-10213) Handle block location for Ozone
[ https://issues.apache.org/jira/browse/IMPALA-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Smith resolved IMPALA-10213.
------------------------------------
Fix Version/s: Impala 4.2.0
Resolution: Fixed
> Handle block location for Ozone
> -------------------------------
>
> Key: IMPALA-10213
> URL: https://issues.apache.org/jira/browse/IMPALA-10213
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
> Reporter: Attila Doroszlai
> Assignee: Michael Smith
> Priority: Major
> Fix For: Impala 4.2.0
>
>
> Currently Impala treats Ozone as a remote filesystem, similar to S3A, ADLS etc. Ozone provides block location info in its Hadoop-compatible FS implementations. Also, Ozone can be colocated with Impala daemons. It would be nice if Impala could be improved to use Ozone's location info to support locality of execution.
> Look into unit tests to validate that reads in the mini-cluster are DISK_LOCAL rather than REMOTE.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)