Github user dyozie commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/22#discussion_r84121208
--- Diff: reference/cli/admin_utilities/hawqinit.html.md.erb ---
@@ -40,11 +40,17 @@ where:
The `hawq init <object>` utility will create a HAWQ instance using
configuration parameters defined in `$GPHOME/etc/hawq-site.xml`. Before running
this utility, make sure that you have installed the HAWQ software on all the
hosts in the array.
-In a HAWQ DBMS, each database instance (the master and all segments) must
be initialized across all of the hosts in the system in such a way that they
can all work together as a unified DBMS. The `hawq init cluster` utility takes
care of initializing the HAWQ master and each segment instance, and configuring
the system as a whole. When hawq init cluster is run, the cluster comes online
automatically without needing to explicitly start it. A single node cluster can
be started without any user-defined changes to the default `hawq-site.xml`
file. The template-hawq-site.xml file is used to specify the configuration for
larger clusters.
+In a HAWQ DBMS, each database instance (the master and all segments) must
be initialized across all of the hosts in the system in such a way that they
can all work together as a unified DBMS. The `hawq init cluster` utility takes
care of initializing the HAWQ master and each segment instance, and configuring
the system as a whole. When hawq init cluster is run, the cluster comes online
automatically without needing to explicitly start it. A single node cluster can
be started without any user-defined changes to the default `hawq-site.xml`
file. Use the template-hawq-site.xml file to specify the configuration for
larger clusters.
--- End diff --
Also do a quick edit for passive voice here.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
