[
https://issues.apache.org/jira/browse/IMPALA-14130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956688#comment-17956688
]
Riza Suminto commented on IMPALA-14130:
---------------------------------------
Sorry about that. Csaba also notice this couple weeks ago.
After IMPALA-13850 (part 2), we can tweak the script until it sees
catalog.curr-version >= 100.
https://github.com/apache/impala/blob/d630d6f8af8cd86a845fc0415c99b8aa6608c28f/fe/src/main/java/org/apache/impala/catalog/CatalogServiceCatalog.java#L2297-L2302
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
