Supported operations in SDS

SDS provides the following series of operations for processing tables and records.

Table operations

SDS provides functions for creating, modifying, copying, disabling, enabling, and deleting tables.

• createTable: Create a table with specified table name and schema
• alterTable: Add or delete attributes, modify table permissions, modify read/write quotas, space quota, modify secondary index types, etc.
• cloneTable: Copy from an existing table to one with same content but different table name
• disableTable: Temporarily set table offline
• enableTable: Put table back online
• dropTable: Drop/remove the table

In addition, SDS also provides findAllTables operation for users to obtain all tables under their account, and via describeTable operation to retrieve schema and meta data of table.

Table operations can be performed by code, or as recommended, handled on more user-friendly SDS console.

Record operations

You can use record operations to add, update, delete self-increment, or read records.

• Add, update (put): Specify entity group key (if one exists) and primary key. When record not present, it is for add; when record is present, it is for update. You can add/update all or part of attributes. Conditions can be specified. When conditions are met, command is executed
• Increment: For integer numeric attributes, increments can be specified to self-increment them
• Remove: Specify entity group key (if one exists) and primary key, which can delete all or part of attributes. Conditions can be specified. When conditions are met, command is executed
• Get: Specify entity group key (if one exists) and primary key to read all attributes or part of attributes
• Batch: Combine operations, such as put, get, increment, and remove to send to SDS server in batches for reducing network overhead

Scan operations

SDS also supports scan operation for range query. You can scan table’s master record or secondary index record. For scanning a wide range of data, it may consume great amount of resources. It is recommended not to frequently perform tasks such as full table scan. In addition, a scan can also perform query with combined conditions, like SQL Where.