docs: publish v2.2 as latest (#2111)
2 months ago
docs: publish v2.2 as latest (#2111)
2 months ago
docs(embeddings): the chunk offset column is <column>_offset, not _offsets (#2170)
Every page that documents bring-your-own chunked embeddings named the required
offset column '<column_name>_offsets'. The runtime looks for '<column>_offset':
offset_col! in runtime-search generates '{col}_offset', ChunkedSearchIndex
::chunking_offset_col formats the same, and base_col strips '_offset'.
The consequence is silent. EmbeddingTable::base_table_has_embedding_column
looks the column up by that exact name and, unlike the two neighbouring
early-returns, logs nothing when it is missing - it just returns false, so the
column is not treated as precomputed and Spice re-embeds it from scratch.
A user who followed the docs pays for embeddings they already had and gets no
diagnostic explaining why.
The vector-search page already contradicted itself: its 'describe sales'
example for the chunked case shows 'address_offset', matching the code, one
section below the constraint that asked for '_offsets'.
Swept all 11 doc sets and all three page types that carry the claim.
a month ago
docs: publish v2.2 as latest (#2111)
2 months ago
docs(embeddings): the chunk offset column is <column>_offset, not _offsets (#2170)
Every page that documents bring-your-own chunked embeddings named the required
offset column '<column_name>_offsets'. The runtime looks for '<column>_offset':
offset_col! in runtime-search generates '{col}_offset', ChunkedSearchIndex
::chunking_offset_col formats the same, and base_col strips '_offset'.
The consequence is silent. EmbeddingTable::base_table_has_embedding_column
looks the column up by that exact name and, unlike the two neighbouring
early-returns, logs nothing when it is missing - it just returns false, so the
column is not treated as precomputed and Spice re-embeds it from scratch.
A user who followed the docs pays for embeddings they already had and gets no
diagnostic explaining why.
The vector-search page already contradicted itself: its 'describe sales'
example for the chunked case shows 'address_offset', matching the code, one
section below the constraint that asked for '_offsets'.
Swept all 11 doc sets and all three page types that carry the claim.
a month ago