Jack Ye 139138c22e docs: move versioning and branching under Table, split schema from data evolution ...

Versioning and branching are properties of a table, not steps in getting data
in, so they join the Table group. Consistency stays with Ingestion, where the
question it answers -- when do other writers' rows become visible -- is asked.

The Ingesting Data page was in the Table group while an Ingestion overview
existed separately, so the two are merged. The large-dataset section was
duplicated between it and the insert page; the insert page keeps it.

Schema and Data Evolution covered two different things under one title.
Changing a table's shape stays in Table management; deriving values from data
already there becomes a Feature engineering page, next to computed columns and
functions, which are the same job at larger scale.

2026-09-09 23:23:14 -07:00

..

delete.mdx

docs: restructure the Documentation tab around catalog objects

2026-09-09 21:33:24 -07:00

index.mdx

docs: move versioning and branching under Table, split schema from data evolution

2026-09-09 23:23:14 -07:00

insert.mdx

docs: move versioning and branching under Table, split schema from data evolution

2026-09-09 23:23:14 -07:00

merge-insert.mdx

docs: restructure the Documentation tab around catalog objects

2026-09-09 21:33:24 -07:00

update.mdx

docs: restructure the Documentation tab around catalog objects

2026-09-09 21:33:24 -07:00