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 "Riza Suminto (Jira)" <ji...@apache.org> on 2025/06/11 16:48:00 UTC

[jira] [Resolved] (IMPALA-14130) start-impala-cluster.py needs to work without tables loaded

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

Riza Suminto resolved IMPALA-14130.
-----------------------------------
     Fix Version/s: Impala 5.0.0
    Target Version: Impala 5.0.0
        Resolution: Fixed

> start-impala-cluster.py needs to work without tables loaded
> -----------------------------------------------------------
>
>                 Key: IMPALA-14130
>                 URL: https://issues.apache.org/jira/browse/IMPALA-14130
>             Project: IMPALA
>          Issue Type: Task
>          Components: Infrastructure
>    Affects Versions: Impala 5.0.0
>            Reporter: Joe McDonnell
>            Assignee: Riza Suminto
>            Priority: Major
>             Fix For: Impala 5.0.0
>
>
> IMPALA-13850 changed the behavior of bin/start-impala-cluster.py to wait for the number of tables to be at least one. This is needed to detect that the catalog has seen at least one update. There is special logic in dataload to start Impala without tables in that circumstance.
> This broke the perf-AB-test job, which starts Impala before loading data. There are other times when we want to start Impala without tables, and it is inconvenient to need to specify --wait_num_tables each time.
> We should detect the catalog update by some means other than the number of tables, and it needs to work without requiring data to be loaded. Maybe the number of databases could work.



--
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