Skip to content

Table Storage

Compatible with the azure-data-tables SDKs (Java, Python, Node.js) and Azurite-style connection strings. Speaks the Azure Table REST protocol with OData/JSON payloads and Shared Key authentication.

HTTP-only: no Docker. Data is held by the configured storage backend (memory by default; persistent, hybrid, or wal for durability).


Features

  • Tables: Create, Delete, List; duplicate create returns 409 TableAlreadyExists. Table names are case-insensitive, as on Azure: MyTable and mytable are one table, listed in the spelling it was created with
  • Entities: Insert, Update (replace/merge), Upsert, Delete, Get by PartitionKey + RowKey; missing entity returns the Azure 404 ResourceNotFound shape, and any entity operation or $batch change against a table that was never created (or was deleted) returns 404 TableNotFound
  • Query: $filter OData expressions: equality on PartitionKey/RowKey, numeric comparisons, and combinations; $select projects a subset of properties
  • Pagination: large result sets are paged with continuation tokens (x-ms-continuation-Next* headers)
  • Optimistic concurrency: ETag / If-Match on update and delete; a stale ETag is rejected
  • Batch transactions: $batch multipart change sets are applied atomically
  • Verb tunneling: an X-HTTP-Method header (MERGE, PATCH, DELETE, GET) overrides the request verb of a single entity request. Inside a $batch change set the write overrides (MERGE, PATCH, DELETE) apply; a change set does not serve reads. The Python SDK sends Merge and Upsert as POST with X-HTTP-Method: MERGE whenever the endpoint host is localhost
  • Table ACL: Get and Set Table ACL ({table}?comp=acl) store up to five stored access policies as SignedIdentifiers XML on the table; a sixth policy, or a permission outside raud, is rejected with 400 InvalidXmlDocument. The policies are stored and returned but not enforced (see SAS below)
  • Service properties: restype=service&comp=properties returns a static <StorageServiceProperties> document (logging and metrics disabled); Set is accepted as a no-op

Endpoint

http://localhost:4577/{account}-table/Tables                                   # table operations
http://localhost:4577/{account}-table/{table}(PartitionKey='p',RowKey='r')     # entity operations
http://localhost:4577/{account}-table/{table}?comp=acl                         # table ACL
http://localhost:4577/{account}-table/$batch                                   # batch transactions

Quickstart

from azure.data.tables import TableServiceClient

conn = ("DefaultEndpointsProtocol=http;AccountName=devstoreaccount1;"
        "AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==;"
        "TableEndpoint=http://localhost:4577/devstoreaccount1-table;")
svc = TableServiceClient.from_connection_string(conn)
table = svc.create_table("people")
table.upsert_entity({"PartitionKey": "team", "RowKey": "alice", "role": "eng"})
for e in table.query_entities("PartitionKey eq 'team'"):
    print(e["RowKey"], e["role"])

The well-known Azurite development key (Eby8vdM0…) is accepted; any account name works.

Configuration

floci-az:
  services:
    table:
      enabled: true
  storage:
    services:
      table:
        # mode: persistent     # override the global storage.mode for table only
        flush-interval-ms: 5000
Property Env var Default Description
enabled FLOCI_AZ_SERVICES_TABLE_ENABLED true Enables the Table Storage service
storage.services.table.mode FLOCI_AZ_STORAGE_SERVICES_TABLE_MODE (inherits storage.mode) Per-service backend override (memory / persistent / hybrid / wal)
storage.services.table.flush-interval-ms FLOCI_AZ_STORAGE_SERVICES_TABLE_FLUSH_INTERVAL_MS 5000 Background flush-to-disk interval for the hybrid mode only; ignored by memory / persistent / wal (wal compacts on storage.wal.compaction-interval-ms instead)

Intentional deviations

  • Shared Key signatures are accepted but not cryptographically verified.
  • The $filter grammar is a practical subset: equality, numeric comparison, and basic boolean composition are supported; full OData functions (substringof, startswith, datetime arithmetic) are not.
  • No SAS enforcement: SAS query parameters are parsed but not validated.