kudu-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From granthe...@apache.org
Subject [kudu] branch master updated: [quickstart] Fix a couple typos in the NiFi guide
Date Wed, 31 Jul 2019 21:35:09 GMT
This is an automated email from the ASF dual-hosted git repository.

granthenke pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git

The following commit(s) were added to refs/heads/master by this push:
     new 5071386  [quickstart] Fix a couple typos in the NiFi guide
5071386 is described below

commit 50713864195df24e1777ee592887b88c57f6985b
Author: Grant Henke <granthenke@apache.org>
AuthorDate: Wed Jul 31 08:57:58 2019 -0500

    [quickstart] Fix a couple typos in the NiFi guide
    Changes cluster to container given Nifi is a single
    node in this example.
    Change-Id: I008ef2550edea06dafb58bc7e8e408e57d255269
    Reviewed-on: http://gerrit.cloudera.org:8080/13964
    Tested-by: Grant Henke <granthenke@apache.org>
    Reviewed-by: Andrew Wong <awong@cloudera.com>
 examples/quickstart/nifi/README.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/examples/quickstart/nifi/README.adoc b/examples/quickstart/nifi/README.adoc
index 3d4e168..05626dc 100644
--- a/examples/quickstart/nifi/README.adoc
+++ b/examples/quickstart/nifi/README.adoc
@@ -22,7 +22,7 @@ You can view the running NiFi instance at link:http://localhost:8080/nifi[localh
 NOTE: `--network="docker_default"` is specified to connect the container the
 same network as the quickstart cluster.
-NOTE: You can include the `-d` flag to run the cluster in the background.
+NOTE: You can include the `-d` flag to run the container in the background.
 == Create the Kudu table
@@ -117,7 +117,7 @@ Once you are done with the NiFi container you can shutdown in a couple
of ways.
 If you ran NiFi without the `-d` flag, you can use `ctrl + c` to stop the  container.
 If you ran NiFi with the `-d` flag, you can use the following to
-gracefully shutdown the cluster:
+gracefully shutdown the container:

View raw message