Internally Deployed Buckets
Breakdown of the Ascend internal Blob Bucket/Containers
An Ascend deployment creates the following blob buckets/containers (depending on cloud provider nomenclature):
| Bucket Name | Description |
|---|---|
| {env-id}-tmp | Stores intermediate staging data |
| {env-id}-sample-data | Reserved, not used |
| {env-id}-query | Stores metadata used by the Ascend query service |
| {env-id}-record-fragments | Stores the records used by components |
| {env-id}-byte-fragments | Stores binary backups for legacy Read Connectors |
| {env-id}-notebook | Stores Jupyter notebooks (for early access Jupyter notebook deployments) |
| {env-id}-metadata-fragments | Stores data plane fragments metadata used by the Ascend scheduler service |
| {env-id}-eventlog | Stores Spark history logs for Spark history server |
| {env-id}-default | Stores metadata, serves as a staging area for Ascend Read/Write Connectors, and the default bucket for blob store requirements |
| {env-id}-logs | Stores internal logs |
Updated 10 months ago