IMPALA-6303: [DOCS] Fix incorrect mention of DataNodes The documentation on Impala Components (https://impala.apache.org/ docs/build/html/topics/impala_components.html) incorrectly states "... catalog service relays the metadata changes from Impala SQL statements to all the DataNodes in a cluster ...", which is not correct. It should be Impala daemons, instead of 'DataNodes'"
Change-Id: I2116b1f78ef6fa89eafe2126034699d2961c06f6 Reviewed-on: http://gerrit.cloudera.org:8080/9160 Reviewed-by: Michael Brown <mi...@cloudera.com> Tested-by: Impala Public Jenkins Project: http://git-wip-us.apache.org/repos/asf/impala/repo Commit: http://git-wip-us.apache.org/repos/asf/impala/commit/4e5f0393 Tree: http://git-wip-us.apache.org/repos/asf/impala/tree/4e5f0393 Diff: http://git-wip-us.apache.org/repos/asf/impala/diff/4e5f0393 Branch: refs/heads/2.x Commit: 4e5f0393e33ed37af89299a100cad93dca2300b6 Parents: db0f381 Author: sujithjay <suj...@hotmail.com> Authored: Tue Jan 30 23:15:47 2018 +0530 Committer: Impala Public Jenkins <impala-public-jenk...@gerrit.cloudera.org> Committed: Fri Feb 2 01:10:15 2018 +0000 ---------------------------------------------------------------------- docs/topics/impala_components.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/impala/blob/4e5f0393/docs/topics/impala_components.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_components.xml b/docs/topics/impala_components.xml index 63090d5..1a6ddb9 100644 --- a/docs/topics/impala_components.xml +++ b/docs/topics/impala_components.xml @@ -137,7 +137,7 @@ under the License. <p> The Impala component known as the <term>catalog service</term> relays the metadata changes from Impala SQL - statements to all the DataNodes in a cluster. It is physically represented by a daemon process named + statements to all the Impala daemons in a cluster. It is physically represented by a daemon process named <codeph>catalogd</codeph>; you only need such a process on one host in the cluster. Because the requests are passed through the statestore daemon, it makes sense to run the <cmdname>statestored</cmdname> and <cmdname>catalogd</cmdname> services on the same host.
