[
https://issues.apache.org/jira/browse/HAWQ-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824695#comment-15824695
]
ASF GitHub Bot commented on HAWQ-1263:
--------------------------------------
Github user dyozie commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/86#discussion_r96317322
--- Diff: markdown/ddl/ddl-database.html.md.erb ---
@@ -2,77 +2,75 @@
title: Creating and Managing Databases
---
-A HAWQ system is a single instance of HAWQ. There can be several separate
HAWQ systems installed, but usually just one is selected by environment
variable settings. See your HAWQ administrator for details.
-
-There can be multiple databases in a HAWQ system. This is different from
some database management systems \(such as Oracle\) where the database instance
*is* the database. Although you can create many databases in a HAWQ system,
client programs can connect to and access only one database at a time — you
cannot cross-query between databases.
+Your HAWQ deployment may have multiple databases. This is different from
some database management systems \(such as Oracle\) where the database instance
*is* the database. Although you can create many databases in a HAWQ system,
client programs can connect to and access only one database at a time — you
cannot cross-query between databases.
## <a id="topic3"></a>About Template Databases
-Each new database you create is based on a *template*. HAWQ provides a
default database, *template1*. Use *template1* to connect to HAWQ for the first
time. HAWQ uses *template1* to create databases unless you specify another
template. Do not create any objects in *template1* unless you want those
objects to be in every database you create.
+Each new database you create is based on a *template*. HAWQ provides a
default database, `template1`. HAWQ uses `template1` to create databases unless
you specify another template. Do not create any objects in `template1` unless
you want those objects to be in every database you create.
-HAWQ uses two other database templates, *template0* and *postgres*,
internally. Do not drop or modify *template0* or *postgres*. You can use
*template0* to create a completely clean database containing only the standard
objects predefined by HAWQ at initialization, especially if you modified
*template1*.
+HAWQ uses two other database templates internally, `template0` and
`postgres`. Do not drop or modify `template0` or `postgres`. You can use
`template0` to create a completely clean database containing only the standard
objects predefined by HAWQ at initialization, especially if you have modified
`template1`.
--- End diff --
", especially if you have modified `template1`" -> ". This may be necessary
if you have modified `template1`."
This also implies that template0 and template1 are the same - is that
correct?
> docs - miscellaneous improvements
> ---------------------------------
>
> Key: HAWQ-1263
> URL: https://issues.apache.org/jira/browse/HAWQ-1263
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Documentation
> Reporter: Lisa Owen
> Assignee: David Yozie
> Priority: Minor
>
> ambari rest api:
> - add warning about using http delete requests
> - use AMBARI instead of AMB in env varbs for clarity
> - add link from main ambari doc to rest apis and adjust subnav accordingly
> intro to hawq op env:
> - include info about PATH and LD_LIBRARY_PATH settings
> - add pxf log file directory to table of important files/dirs
> gpfdist:
> - correct example for single instance
> aws configuration
> - more info re: storage types and security groups
> - update instance types table
> ddl database
> - clarify that you can only clone from a template database
> - various other wording and formatting fixes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
