Amazon Technologies, Inc.

Shirley Xue Yi Ly

Kiran Kumar Muniswamy Reddy

Pejus Manoj Das

Wei Xiao

Aanchal Gupta

Yijun Lu

Adam Douglas Morley

Lokendra Singh Panwar

A distributed data storage system may implement determining indexing progress for a table stored in the distributed data storage system. A table may be stored in multiple table partitions. When a secondary index is created for the table, each partition may independently index the items stored within the table partition in order to identify those items in the partition that should be stored in the secondary index. During creation of the secondary index, creation progress points that indicate the progress of the indexing across the table partitions may be determined. The creation progress points may be provided via a programmatic, textual, or graphical interface to the distributed data storage system.

Determining indexing progress for a table in a distributed data store

A data storage system may implement generating creation performance metrics for a secondary index of a table. Metrics may be collected from different partitions of a table and different partitions of a secondary index in a table store upon initiating creation of the secondary index for the table that utilize provisioned resources for creating the secondary index. The metrics may be analyzed to generate performance metrics for the creation of the table. The performance metrics may be provided to clients of the data store or to monitoring systems. Monitoring systems may send performance event notifications to clients or automatically perform modifications to the provisioned throughput capacity.

Generating creation performance metrics for a secondary index of a table

A non-relational data store may implement validating and non-validating secondary indexes for a table. Operations at a table for a given item may be performed when indexing the item to create a secondary index or when updates to the given item are received. Attribute values of a given item may be validated with respect to an indexing schema for the secondary index. For a non-validating secondary index, validation errors detected for the attribute values may be ignored so that the operation at the table may be performed. For a validating secondary index, validation errors detected for the attribute values may result in denying performance of the operation. In some embodiments, a secondary index from may be changed from validating to non-validating, or non-validating to validating.

Validating and non-validating secondary indexes for a table in a non-relational data store

Growing community of inventors

Bellevue, WA, United States of America

Shirley Xue Yi Ly