Skip to content

Clarify hash-addressed vs schema-addressed storage distinction #118

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dimitri-yatsenko wants to merge 3 commits into from
Closed

Clarify hash-addressed vs schema-addressed storage distinction #118

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
088ab03
docs: regenerate LLM files with corrected migration guide links
dimitri-yatsenko Jan 14, 2026
3b89db7
Merge remote-tracking branch 'origin/main'
dimitri-yatsenko Jan 14, 2026
0dcdd93
docs: clarify hash-addressed vs schema-addressed storage distinction
dimitri-yatsenko Jan 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 9 additions & 5 deletions src/how-to/use-object-storage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,12 +8,16 @@ An **Object-Augmented Schema** extends relational tables with object storage as

OAS supports two addressing schemes:

| Addressing | Location | Path Derived From | Use Case |
|------------|----------|-------------------|----------|
| **Hash-addressed** | Object store | Content hash (MD5) | Blobs, attachments (with deduplication) |
| **Schema-addressed** | Object store | Schema structure | NumPy arrays, Zarr, HDF5 (browsable paths) |
| Addressing | Location | Path Derived From | Object Type | Use Case |
|------------|----------|-------------------|-------------|----------|
| **Hash-addressed** | Object store | Content hash (MD5) | Individual/atomic | Single blobs, single files, attachments (with deduplication) |
| **Schema-addressed** | Object store | Schema structure | Complex/multi-part | Zarr arrays, HDF5 datasets, multi-file objects (browsable paths) |

Data can also be stored **inline** directly in the database column (no `@` modifier).
**Key distinction:**
- **Hash-addressed** (`<blob@>`, `<attach@>`) stores individual, atomic objects - one object per field
- **Schema-addressed** (`<npy@>`, `<object@>`) can store complex, multi-part objects like Zarr (directory structures with multiple files)

Data can also be stored **in-table** directly in the database column (no `@` modifier).

For complete details, see the [Type System specification](../reference/specs/type-system.md).

Expand Down
Loading