Skip to content

Conversation

@jfw-ppi
Copy link
Contributor

@jfw-ppi jfw-ppi commented Dec 28, 2025

Which issue(s) this PR fixes:

#5671

spark.sql.execution.arrow.pyspark.enabled: "true"
# Optional: spill large materializations to the staging location instead of collecting in the driver
staging_location: "s3://my-bucket/tmp/feast"
staging_allow_materialize: true
Copy link
Member

Choose a reason for hiding this comment

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

Do you think staging_allow_materialize flag is redundant here? If staging_location is set, staging should likely be enabled by default.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

Copy link
Member

@ntkathole ntkathole left a comment

Choose a reason for hiding this comment

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

Looks good

Signed-off-by: Jacob Weinhold <29459386+jfw-ppi@users.noreply.github.com>
…st-dev#5671))

Signed-off-by: Jacob Weinhold <29459386+jfw-ppi@users.noreply.github.com>
@ntkathole ntkathole force-pushed the 5671-spark-staging-only branch from b3ba611 to e8e9163 Compare January 2, 2026 08:00
@ntkathole ntkathole merged commit 5b787af into feast-dev:master Jan 2, 2026
14 of 17 checks passed
@jfw-ppi jfw-ppi deleted the 5671-spark-staging-only branch January 2, 2026 09:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants