[
https://issues.apache.org/jira/browse/IMPALA-14040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17950480#comment-17950480
]
ASF subversion and git services commented on IMPALA-14040:
----------------------------------------------------------
Commit ad19828df5ab45704c9b034813dd67a1571d3f45 in impala's branch
refs/heads/master from Peter Rozsa
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=ad19828df ]
IMPALA-14040: Remove Kudu masters property from FeCatalog
This change removes getDefaultKuduMasterHosts from FeCatalog and makes
the Kudu masters lookup bound directly to the backend config.
Tests are adjusted for the new property lookup.
Change-Id: Idcf31a724bb7bd00268accf21c0b997d92e9b23a
Reviewed-on: http://gerrit.cloudera.org:8080/22863
Reviewed-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Daniel Becker <[email protected]>
Tested-by: Daniel Becker <[email protected]>
> Remove Kudu masters property from FeCatalog
> -------------------------------------------
>
> Key: IMPALA-14040
> URL: https://issues.apache.org/jira/browse/IMPALA-14040
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Reporter: Peter Rozsa
> Assignee: Peter Rozsa
> Priority: Minor
>
> DEFAULT_KUDU_MASTER_HOSTS is instantiated statically, and later on, it's
> passed to one of the catalog implementations and it's stored as a catalog
> member. Instead, it could be looked up from the backend flags. With this
> approach, the argument pushdown can be eliminated from the catalog's ctor and
> removed from the FeCatalog interface as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]