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 "Zoltán Borók-Nagy (Jira)" <ji...@apache.org> on 2026/04/24 15:36:00 UTC

[jira] [Updated] (IMPALA-14923) Run Iceberg tests with no block locations

     [ https://issues.apache.org/jira/browse/IMPALA-14923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zoltán Borók-Nagy updated IMPALA-14923:
---------------------------------------
    Description: 
When block locations are not available Impala works quite differently. E.g. it doesn't create TScanRanges in the Frontend, but generates them in the backend from TFileSplitGeneratorSpec objects.

It is possible to disable block location information via core-site.xml:
{noformat}
     <property>
        <name>impala.preload-block-locations-for-scheduling</name>
        <value>false</value>
     </property>
{noformat}
 
Executing a set of tests with disabled block locations could catch a few errors in time.

  was:
When block locations are not available Impala works quite differently. E.g. it doesn't create TScanRanges in the Frontend, but generates them in the backend from TFileSplitGeneratorSpec objects.

It is possible to disable block location information via core-site.xml:
{noformat}
     <property>
        <name>impala.preload-block-locations-for-scheduling</name>
        <value>false</value>
      </property>
{noformat}
 
Executing a set of tests with disabled block locations could catch a few errors in time.


> Run Iceberg tests with no block locations
> -----------------------------------------
>
>                 Key: IMPALA-14923
>                 URL: https://issues.apache.org/jira/browse/IMPALA-14923
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure, Test
>            Reporter: Zoltán Borók-Nagy
>            Assignee: Zoltán Borók-Nagy
>            Priority: Major
>              Labels: impala-iceberg
>
> When block locations are not available Impala works quite differently. E.g. it doesn't create TScanRanges in the Frontend, but generates them in the backend from TFileSplitGeneratorSpec objects.
> It is possible to disable block location information via core-site.xml:
> {noformat}
>      <property>
>         <name>impala.preload-block-locations-for-scheduling</name>
>         <value>false</value>
>      </property>
> {noformat}
>  
> Executing a set of tests with disabled block locations could catch a few errors in time.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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