BigQuery feature comparison: historical analysis
Why this page is archived
The current BigQuery dependency has changed materially since this analysis. Features described here as absent or planned—including bounded scripting, materialized-view emulation, external-data paths, Storage API profiles, broader INFORMATION_SCHEMA, grouping extensions, TABLESAMPLE, and search/vector behavior—now have newer source or test evidence.
LocalCloud still lacks a pinned, qualified dependency image and assembled-image digest. That means the old analysis cannot simply be inverted into a current support matrix either.
Historical status
| Earlier analysis surface | Current disposition |
|---|---|
| Feature rows and planned phases | Historical; use the current operation contract. |
| Fixed counts and broad support labels | Withdrawn until immutable release qualification exists. |
| Parser or DuckDB risk categories | Still useful as design-review prompts, not compatibility results. |
Use the current references
- BigQuery emulator feature reference — feature-specific evidence states and release boundaries.
- BigQuery service contract — operation-level LocalCloud contract.
- Compatibility matrix — evidence states across all runtime services.
Historical value
This analysis remains useful for understanding design risks that still matter:
- a parser accepting syntax does not prove correct execution;
- DuckDB and BigQuery can differ in coercion, errors, numeric behavior, geography, and distributed semantics;
- metadata-only or empty compatibility surfaces are not production behavior;
- infrastructure systems such as reservations, billing, quotas, IAM, and audit logging require separate treatment.
Do not use this page to approve a feature, client, language SDK, or release. Use an immutable dependency revision, assembled image digest, qualification result, and durable evidence record instead.
This comment is sent to PostHog. Do not include secrets, personal data, or customer data. See Privacy.