Merge pull request #177 from datastax/phil/doc-edits

updating reference to current parameter .writetime.names rather than …

Author: msmygit

src/resources/cdm-detailed.properties

@@ -115,7 +115,7 @@ spark.cdm.schema.origin.keyspaceTable                keyspace_name.table_name
 #    .mismatch            : Default is false. when true, data that is different between Origin and Target
 #                           will be reconciled. It is important to note that TIMESTAMP will have an effect
 #                           here - if the WRITETIME of the Origin record (determined with
-#                           .writetime.indexes) is earlier than the WRITETIME of the Target record, the
+#                           .writetime.names) is earlier than the WRITETIME of the Target record, the
 #                           change will not appear in Target. This may be particularly challenging to
 #                           troubleshoot if individual columns (cells) have been modified in Target.
 #
@@ -205,7 +205,7 @@ spark.cdm.perfops.ratelimit.target                40000
 #                                    the record in Origin cannot be determined (such as the only non-key
 #                                    columns are collections). This parameter allows a crude constant value
 #                                    to be used in its place, and overrides
-#                                    .schema.origin.column.writetime.indexes.
+#                                    .schema.origin.column.writetime.names.
 #      .writetime.incrementBy        Default is 0. This is useful when you have a List that is not frozen,
 #                                    and are updating this via the autocorrect feature. Lists are not idempotent,
 #                                    and subsequent UPSERTs would add duplicates to the list. Future versions
@@ -263,14 +263,14 @@ spark.cdm.perfops.ratelimit.target                40000
 #                       split. Invalid percentages will be treated as 100.
 #
 #    .writetime       : Filter records based on their writetimes. The maximum writetime of the columns 
-#                       configured at .schema.origin.column.writetime.indexes will be compared to the 
-#                       thresholds, which must be in microseconds since the epoch. If the .writetime.indexes 
+#                       configured at .schema.origin.column.writetime.names will be compared to the
+#                       thresholds, which must be in microseconds since the epoch. If the .writetime.names
 #                       are not specified, or the thresholds are null or otherwise invalid, the filter will 
 #                       be ignored. Note that .perfops.batchSize will be ignored when this filter is in place,
 #                       a value of 1 will be used instead.#                      
 #       .min          : Lowest (inclusive) writetime values to be migrated
 #       .max          : Highest (inclusive) writetime values to be migrated
-#                       maximum timestamp of the columns specified by .schema.origin.column.writetime.indexes,
+#                       maximum timestamp of the columns specified by .schema.origin.column.writetime.names,
 #                       and if that is not specified, or is for some reason null, the filter is ignored.
 #
 #    .column          : Filter rows based on matching a configured value.

src/resources/cdm.properties

@@ -77,7 +77,7 @@ spark.cdm.schema.origin.keyspaceTable                keyspace_name.table_name
 #    .mismatch            : Default is false. when true, data that is different between Origin and Target
 #                           will be reconciled. It is important to note that TIMESTAMP will have an effect
 #                           here - if the WRITETIME of the Origin record (determined with
-#                           .writetime.indexes) is earlier than the WRITETIME of the Target record, the
+#                           .writetime.names) is earlier than the WRITETIME of the Target record, the
 #                           change will not appear in Target. This may be particularly challenging to
 #                           troubleshoot if individual columns (cells) have been modified in Target.
 #-----------------------------------------------------------------------------------------------------------