Repository navigation
feat: declare and backfill expression-computed columns - #360
Merged
Merged
Conversation
AddColumnsEntry gains a computed member for maintained SQL-expression columns: declared all-null with the expression persisted as the binding, type and inputs inferred server-side, filled by backfill rather than at declaration. The backfill route description widens from UDF-backed columns to cover expression-computed ones, matching the deployed server. Generated clients regenerated.
github-actions
Bot
added
enhancement
wkalt
added a commit
to lancedb/lancedb
that referenced
this pull request
Aug 14, 2026
LanceDB Cloud and Enterprise support computed columns through the REST API,
so declaration dispatches per backend: local tables plan the expression
themselves, remote ones send {name, computed} entries for the server to
plan. A remote refresh is the server's backfill job -- refresh_column_async
submits it and returns a handle whose successful wait establishes a
read-freshness baseline on the submitting handle, unless a checkout has
pinned the handle by the time the job completes; the blocking form refuses
rather than invent a fill count the server does not report.
The {name, computed} member matches the deployed enterprise server contract
(lance-format/lance-namespace#360).
wkalt
added a commit
to lancedb/lancedb
that referenced
this pull request
Aug 14, 2026
LanceDB Cloud and Enterprise support computed columns through the REST API,
so declaration dispatches per backend: local tables plan the expression
themselves, remote ones send {name, computed} entries for the server to
plan. A remote refresh is the server's backfill job -- refresh_column_async
submits it and returns a handle whose successful wait establishes a
read-freshness baseline on the submitting handle, unless a checkout has
pinned the handle by the time the job completes; the blocking form refuses
rather than invent a fill count the server does not report.
The {name, computed} member matches the deployed enterprise server contract
(lance-format/lance-namespace#360).
wkalt
added a commit
to lancedb/lancedb
that referenced
this pull request
Aug 14, 2026
LanceDB Cloud and Enterprise support computed columns through the REST API,
so declaration dispatches per backend: local tables plan the expression
themselves, remote ones send {name, computed} entries for the server to
plan. A remote refresh is the server's backfill job -- refresh_column_async
submits it and returns a handle whose successful wait establishes a
read-freshness baseline on the submitting handle, unless a checkout has
pinned the handle by the time the job completes; the blocking form refuses
rather than invent a fill count the server does not report.
The {name, computed} member matches the deployed enterprise server contract
(lance-format/lance-namespace#360).
wkalt
added a commit
to lancedb/lancedb
that referenced
this pull request
Aug 14, 2026
LanceDB Cloud and Enterprise support computed columns through the REST API,
so declaration dispatches per backend: local tables plan the expression
themselves, remote ones send {name, computed} entries for the server to
plan. A remote refresh is the server's backfill job -- refresh_column_async
submits it and returns a handle whose successful wait establishes a
read-freshness baseline on the submitting handle, unless a checkout has
pinned the handle by the time the job completes; the blocking form refuses
rather than invent a fill count the server does not report.
The {name, computed} member matches the deployed enterprise server contract
(lance-format/lance-namespace#360).
wkalt
added a commit
to lancedb/lancedb
that referenced
this pull request
Aug 14, 2026
LanceDB Cloud and Enterprise support computed columns through the REST API,
so declaration dispatches per backend: local tables plan the expression
themselves, remote ones send {name, computed} entries for the server to
plan. A remote refresh is the server's backfill job -- refresh_column_async
submits it and returns a handle whose successful wait establishes a
read-freshness baseline on the submitting handle, unless a checkout has
pinned the handle by the time the job completes; the blocking form refuses
rather than invent a fill count the server does not report.
The {name, computed} member matches the deployed enterprise server contract
(lance-format/lance-namespace#360).
wkalt
added a commit
to lancedb/lancedb
that referenced
this pull request
Aug 14, 2026
LanceDB Cloud and Enterprise support computed columns through the REST API,
so declaration dispatches per backend: local tables plan the expression
themselves, remote ones send {name, computed} entries for the server to
plan. A remote refresh is the server's backfill job -- refresh_column_async
submits it and returns a handle whose successful wait establishes a
read-freshness baseline on the submitting handle, unless a checkout has
pinned the handle by the time the job completes; the blocking form refuses
rather than invent a fill count the server does not report.
The {name, computed} member matches the deployed enterprise server contract
(lance-format/lance-namespace#360).
Xuanwo
approved these changes
Aug 14, 2026
wkalt
added a commit
to lancedb/lancedb
that referenced
this pull request
Aug 14, 2026
LanceDB Cloud and Enterprise support computed columns through the REST API,
so declaration dispatches per backend: local tables plan the expression
themselves, remote ones send {name, computed} entries for the server to
plan. A remote refresh is the server's backfill job -- refresh_column_async
submits it and returns a handle whose successful wait establishes a
read-freshness baseline on the submitting handle, unless a checkout has
pinned the handle by the time the job completes; the blocking form refuses
rather than invent a fill count the server does not report.
The {name, computed} member is part of the published namespace contract
(lance-format/lance-namespace#360, merged as de7d5b94e).
wkalt
added a commit
to lancedb/lancedb
that referenced
this pull request
Aug 14, 2026
LanceDB Cloud and Enterprise support computed columns through the REST API,
so declaration dispatches per backend: local tables plan the expression
themselves, remote ones send {name, computed} entries for the server to
plan. A remote refresh is the server's backfill job -- refresh_column_async
submits it and returns a handle whose successful wait establishes a
read-freshness baseline on the submitting handle, unless a checkout has
pinned the handle by the time the job completes; the blocking form refuses
rather than invent a fill count the server does not report.
The {name, computed} member is part of the published namespace contract
(lance-format/lance-namespace#360, merged as de7d5b94e).
wkalt
added a commit
to lancedb/lancedb
that referenced
this pull request
Aug 14, 2026
LanceDB Cloud and Enterprise support computed columns through the REST API,
so declaration dispatches per backend: local tables plan the expression
themselves, remote ones send {name, computed} entries for the server to
plan. A remote refresh is the server's backfill job -- refresh_column_async
submits it and returns a handle whose successful wait establishes a
read-freshness baseline on the submitting handle, unless a checkout has
pinned the handle by the time the job completes; the blocking form refuses
rather than invent a fill count the server does not report.
The {name, computed} member is part of the published namespace contract
(lance-format/lance-namespace#360, merged as de7d5b94e).
wkalt
added a commit
to lancedb/lancedb
that referenced
this pull request
Aug 14, 2026
LanceDB Cloud and Enterprise support computed columns through the REST API,
so declaration dispatches per backend: local tables plan the expression
themselves, remote ones send {name, computed} entries for the server to
plan. A remote refresh is the server's backfill job -- refresh_column_async
submits it and returns a handle whose successful wait establishes a
read-freshness baseline on the submitting handle, unless a checkout has
pinned the handle by the time the job completes; the blocking form refuses
rather than invent a fill count the server does not report.
The {name, computed} member is part of the published namespace contract
(lance-format/lance-namespace#360, merged as de7d5b94e).
wkalt
added a commit
to lancedb/lancedb
that referenced
this pull request
Aug 14, 2026
LanceDB Cloud and Enterprise support computed columns through the REST API,
so declaration dispatches per backend: local tables plan the expression
themselves, remote ones send {name, computed} entries for the server to
plan. A remote refresh is the server's backfill job -- refresh_column_async
submits it and returns a handle whose successful wait establishes a
read-freshness baseline on the submitting handle, unless a checkout has
pinned the handle by the time the job completes; the blocking form refuses
rather than invent a fill count the server does not report.
The {name, computed} member is part of the published namespace contract
(lance-format/lance-namespace#360, merged as de7d5b94e).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AddColumnsEntry gains a computed member for maintained SQL-expression
columns: declared all-null with the expression persisted as the binding,
type and inputs inferred server-side, filled by backfill rather than at
declaration. The backfill route description widens from UDF-backed columns
to cover expression-computed ones, matching the deployed server. Generated
clients regenerated.