Skip to content

fix: read all source columns in BigQuery pulls when the feature list is empty - #7048

Open
Mrun25 wants to merge 1 commit into
feast-dev:masterfrom
Mrun25:fix-bigquery-empty-feature-cols-7047
Open

Mrun25 wants to merge 1 commit into
feast-dev:masterfrom
Mrun25:fix-bigquery-empty-feature-cols-7047

Conversation

@Mrun25

@Mrun25 Mrun25 commented Oct 20, 2026

Copy link
Copy Markdown

What this PR does / why we need it:

FeatureBuilder.get_column_info signals "read all source columns" for BatchFeatureViews with a pandas/python (or ray/flink) UDF by passing an empty feature_name_columns list. BigQueryOfflineStore.pull_all_from_table_or_query and pull_latest_from_table_or_query did not handle the empty case: they built the select list from join keys + feature columns + timestamps, so the generated query selected only the join keys and timestamps. Materializing such a view from BigQuery then failed with ValueError: Column <feature> not found in table because the UDF never received the source columns.

This PR handles the empty list the way the other offline stores do:

  • pull_all_from_table_or_query: SELECT *
  • pull_latest_from_table_or_query: SELECT * in the inner query and SELECT * EXCEPT(_feast_row) in the outer query, so the ROW_NUMBER helper column is not exposed

Explicit (non-empty) feature lists are unchanged. Adds regression tests for both pull paths.

Which issue(s) this PR fixes:

Fixes #7047

Testing

  • New unit tests test_pull_all_empty_feature_columns_selects_all and test_pull_latest_empty_feature_columns_selects_all in tests/unit/infra/offline_stores/test_bigquery.py
  • Full test_bigquery.py + test_bigquery_non_entity_mode.py suites pass locally (38 passed)
  • ruff check and ruff format --check clean

…mpty

BigQueryOfflineStore.pull_all_from_table_or_query and
pull_latest_from_table_or_query built their SELECT list from the join
keys, feature columns, and timestamps only. FeatureBuilder signals
"read all source columns" for BatchFeatureViews with a pandas/python
UDF by passing an empty feature_name_columns list, so the generated
query selected only the join keys and timestamps and materialization
failed with "Column <feature> not found in table".

Handle the empty list the way the other offline stores do: select all
columns (SELECT * in pull_all; SELECT * in the inner query and
SELECT * EXCEPT(_feast_row) in the outer query of pull_latest, which
uses a ROW_NUMBER helper column).

Fixes feast-dev#7047

Signed-off-by: Mrun25 <165297479+Mrun25@users.noreply.github.com>
@Mrun25
Mrun25 requested review from a team and sudohainguyen as code owners October 20, 2026 04:25
Copilot AI balanced review requested due to automatic review settings October 20, 2026 04:25

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BigQuery offline store: materializing a BatchFeatureView with a pandas/python UDF fails with Column <feature> not found in table

2 participants