Distributed Table

Distributed Tables are NoSQL database tables. This class inherits from TopLevelResource and has direct access to the resource’s database object. The following attributes are directly accessible:

attr organization_service_id:
 The ID of the parent organization service (cloud)
attr region_name:
 The region that this table resides in
attr table_id:The provider ID of the distributed table
attr name:The name of this distributed table
attr create_time:
 The time when this distributed table was created
attr status:The status of this table (Creating, active, etc)
attr size:The size in bytes of the table
attr backed_up:Whether or not this table has a backup
attr arn:The Amazon Resource Name of this table
attr encryption_at_rest:
 Boolean value of whether or not this table is encrypted at rest
attr item_count:
 The count of how many items are in this table
attr read_capacity:
 The maximum number of strongly consistent reads consumed per second
attr write_capactiy:
 The maximum number of writes consumed per second
attr stream_specification:
 Boolean value denoting whether or not this table has stream specification enabled
attr global_secondary_indexes:
 Boolean value denoting whether or not this table has one or more global secondary indexes
attr local_secondary_indexes:
 Boolean value denoting whether or not this table has one or more local secondary indexes
attr tags:JSON field of tags for the distributed table
class DivvyResource.Resources.distributedtable.DistributedTable(resource_id)

Bases: DivvyResource.Resources.toplevelresource.TopLevelResource

Distributed Table operations

delete(user_resource_id=None)

Delete this resource. If wrapped with a JobQueue() block, this will queue the deletion job to the wrapped queue, otherwise it calls immediately

distributed_table
distributed_table_id
get_date_created()
static get_db_class()
static get_provider_id_field()
static get_resource_type()
get_supported_actions()
handle_resource_created(user_resource_id=None, project_resource_id=None)

This should be called when a resource is created/discovered after the basic data is added to the database. This gives an opportunity for post-addition hooks (assignment to groups, alerts, etc)

handle_resource_destroyed(user_resource_id=None)

This should be called when a resource is destroyed before the basic data is removed from the database. This gives an opportunity for pre-destruction hooks (removal from groups, alerts, etc)

handle_resource_modified(resource, *args, **kwargs)

This should be called when a resource is modified after the new data has been updated in the DB session This gives an opportunity for post-modification hooks

top_level_resource = True