← 返回首页
Bytewax materializer materializes entire dataset on every pod · Issue #3786 · feast-dev/feast · GitHub
Skip to content

Navigation Menu

Toggle navigation
Sign in
Appearance settings
Search or jump to...

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Resetting focus

Bytewax materializer materializes entire dataset on every pod #3786

New issue
New issue

Description

Expected Behavior

Each pod should materialize a separate batch of data

Current Behavior

Every pod redundantly materializes the entire dataset, causing a massive overspend on processing time and database writes

Steps to reproduce

Observed with snowflake offline store and dynamo db online store. Materialize a feature with enough records for the snowflake s3 integration to output multiple files. View the logs of each pod and add up the total records materialized. Observe that every pod has materialized the entire dataset

Specifications

  • Version: 0.31
  • Platform: fedora linux
  • Subsystem: bytewax batch_engine

Possible Solution

Use JOB_COMPLETION_INDEX in each pods dataflow to select a single file to process

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    • Open in GitHub Copilot app

    Footer

    © 2026 GitHub, Inc.