Summary of Table Service Functionality
Updated: February 11, 2014
The Table service REST API is compliant with the OData Protocol Specification, with some differences, as described in the following sections.
The Table service extends the functionality of OData in the following ways.
The Table service requires that each request be authenticated. Both Shared Key and Shared Key Lite authentication are supported. Shared Key authentication is more secure and is recommended for requests made against the Table service using the REST API.
For more information about authenticating requests, see Authentication for the Azure Storage Services.
A query against the Table service may return a maximum of 1,000 items at one time and may execute for a maximum of five seconds. If the result set contains more than 1,000 items, or if the query did not complete within five seconds, the response includes headers which provide the developer with continuation tokens to use in order to resume the query at the next item in the result set. Continuation token headers may be returned for a Query Tables (REST API) operation or a Query Entities (REST API) operation.
Note that the total time allotted to the request for scheduling and processing the query is 30 seconds, including the five seconds for query execution.
For more information about continuation tokens, see Query Timeout and Pagination.
Every entity in the Table service has two key properties: the PartitionKey property and the RowKey property. These properties together form the table's primary key and uniquely identify each entity in the table.
Both properties require string values. It is the developer's responsibility to provide values for these properties when a new entity is inserted, and to include them in any update or delete operation on an entity.
For more information about these required key properties, see Understanding the Table Service Data Model.
Every entity in the Table service has a Timestamp system property. The Timestamp property is a DateTime value that is maintained on the server side to record the time an entity was last modified. The Table service uses the Timestamp property internally to provide optimistic concurrency. The value of Timestamp is a monotonically increasing value, meaning that each time the entity is modified, the value of Timestamp increases for that entity. This property should not be set on insert or update operations (the value will be ignored).
For more information about the Timestamp property, see Understanding the Table Service Data Model.
The Table service supports batch transactions on entities that are in the same table and belong to the same partition group, which means they have the same PartitionKey value. This allows multiple insert, update, merge, and delete operations to be supported within a single atomic transaction. The Table service supports a subset of the functionality provided by the OData protocol.
For more information about batch operations, see Performing Entity Group Transactions.
The Table service has the following restrictions on functionality provided by OData.
The Table service does not support using the Credentials property of the DataServiceContext class to authenticate a request. Instead, you must authenticate a request against the Table service by adding an Authorization header to the request. For more information, see Authentication for the Azure Storage Services.
Not all property types supported by the OData are supported by the Table service. For a list of supported property types, see Understanding the Table Service Data Model.
The Table service does not currently support links between tables. Links are associative relationships between data.
Projection refers to querying a subset of the properties for an entity or entities. It is analogous to selecting a subset of the columns or properties of a table when querying in LINQ. Projection reduces the amount of data that must be returned by a query by specifying that only certain properties are returned in the response. Projection is supported as part of the 2011-08-18 version of the Windows Azure storage services. For more information, refer to Query Entities (REST API), Writing LINQ Queries Against the Table Service, and OData: Select System Query Option ($select).
The Table service supports using language-integrated queries (LINQ). Only these LINQ query operators are supported for use with the Table service:
For more information, see Query Operators Supported for the Table Service.
OData supports sending payloads in the JSON format. The Windows Azure Table service supports the OData JSON format as of API version 2013-08-15, with the OData data service version set to 3.0; prior versions do not support the JSON format. For more information, see Payload Format for Table Service Operations and Setting the OData Data Service Version Headers.
ConceptsTable Service REST API