Skip to content

feast apply broken with 0.15.* if the registry already exists #2086

@MattDelac

Description

@MattDelac

Expected Behavior

Running feast apply twice in a row should work as expected

Current Behavior

The second time we run feast apply, it will break with feast v0.15.*

Steps to reproduce

  • install Feast 0.15.1
  • Add a local config
project: local
registry: tmp/registry.db
provider: local
offline_store:
    type: bigquery
    dataset: scratch
online_store:
    type: sqlite
    path: tmp/database.db
  • feast apply ✅ if the registry does not exist
  • feast apply 🔴

image

From Slack > And interestingly, it does not always fail on the same FeatureView being applied > And I can successfully print feature_view_proto.spec.entities right before it fails

Specifications

  • Version:
  • Platform:
  • Subsystem:

Possible Solution

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions