name of the table
cold or hot, appended regions are added to hot and after compaction make it into cold. Cold regions can also be compacted
id of the region, for simplicity, at least for now it will be GUID
timestamp when region was created as a result of an append or compact operation
true - its data was compacted into another region, false - it was not compacted
number of records in the region, can be used for optimisation and compaction decisions
all records in the audit table will contain column that shows the last updated time, this will be used to generated ingestion queries
number of records in the region, can be used for optimisation and compaction decisions
timestamp when region was created as a result of an append or compact operation
true - its data was compacted into another region, false - it was not compacted
all records in the audit table will contain column that shows the last updated time, this will be used to generated ingestion queries
id of the region, for simplicity, at least for now it will be GUID
cold or hot, appended regions are added to hot and after compaction make it into cold.
cold or hot, appended regions are added to hot and after compaction make it into cold. Cold regions can also be compacted
name of the table
name of the table
cold or hot, appended regions are added to hot and after compaction make it into cold. Cold regions can also be compacted
id of the region, for simplicity, at least for now it will be GUID
timestamp when region was created as a result of an append or compact operation
true - its data was compacted into another region, false - it was not compacted
number of records in the region, can be used for optimisation and compaction decisions
all records in the audit table will contain column that shows the last updated time, this will be used to generated ingestion queries