You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/10/05 19:10:00 UTC

[jira] [Commented] (IMPALA-10213) Handle block location for Ozone

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

Tim Armstrong commented on IMPALA-10213:
----------------------------------------

[~adoroszlai] are there any docs or other information about how block locality in Ozone works? Is it similar to classic HDFS with 3-way replication, or more like HDFS with erasure coding?

> Handle block location for Ozone
> -------------------------------
>
>                 Key: IMPALA-10213
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10213
>             Project: IMPALA
>          Issue Type: Sub-task
>            Reporter: Attila Doroszlai
>            Priority: Major
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org