[
https://issues.apache.org/jira/browse/TRAFODION-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488517#comment-16488517
]
ASF GitHub Bot commented on TRAFODION-3082:
-------------------------------------------
Github user liuyu000 commented on a diff in the pull request:
https://github.com/apache/trafodion/pull/1575#discussion_r190479988
--- Diff: docs/sql_reference/src/asciidoc/_chapters/sql_statements.adoc ---
@@ -1755,6 +1760,23 @@ for the first column, the values in the second
column are used to order the rows
rows occur in a non-unique index, their order is based on the sequence
specified for the columns of the key of the
underlying table. For ordering (but not for other purposes), nulls are
greater than other values.
+* `populate-option`
+
+** `NO POPULATE`
++
+specifies that the index is not to be populated when it is created.
++
+The index’s partition(s) are created, but no data is written to the index,
and it is marked “offline”. You can drop an offline index with the DROP INDEX
statement.
+The DROP TABLE statement also drops offline indexes of the specified
table.
+DML statements have no effect on offline indexes.
++
+If an index is created with the intention of using it for a constraint, it
must be populated before creating the constraint.
+You can populate an offline index and remove its offline designation by
using the POPULATE INDEX utility.
+
+** `POPULATE`
++
+specifies that the index is to be created and populated.
--- End diff --
Yes, thanks Dave, I've added it 😊⭐️
> Add *populate-option* for *CREATE INDEX Statement* and fix typos in
> *Trafodion SQL Reference Manual*
> ----------------------------------------------------------------------------------------------------
>
> Key: TRAFODION-3082
> URL: https://issues.apache.org/jira/browse/TRAFODION-3082
> Project: Apache Trafodion
> Issue Type: Documentation
> Reporter: Liu Yu
> Assignee: Liu Yu
> Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
