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

Posted to issues@impala.apache.org by "Riza Suminto (Jira)" <ji...@apache.org> on 2024/02/28 18:58:00 UTC

[jira] [Resolved] (IMPALA-12847) Make computeScanRangeLocations and computeStats idempotent in HdfsScanNode.java

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

Riza Suminto resolved IMPALA-12847.
-----------------------------------
    Fix Version/s: Impala 4.4.0
       Resolution: Fixed

> Make computeScanRangeLocations and computeStats idempotent in HdfsScanNode.java
> -------------------------------------------------------------------------------
>
>                 Key: IMPALA-12847
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12847
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Frontend
>            Reporter: Riza Suminto
>            Assignee: Riza Suminto
>            Priority: Major
>             Fix For: Impala 4.4.0
>
>
> After IMPALA-12631, HdfsScanNode.computeScanRangeLocations() need check if countStarSlot_ is null or not to schedule footer range only. HdfsScanNode.computeScanRangeLocations() is called along with HdfsScanNode.init() call.
> An external frontend that has its own count star slot analysis and initialization will need to recompute scan range assignment and stats after HdfsScanNode.init(). Therefore, computeScanRangeLocations() and computeStats() should be made idempotent after init() and exposed to subclasses.



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