feat: Materialization Metrics Capture#374
Open
Manisha4 wants to merge 5 commits into
Open
Conversation
Add a write-time metrics capture layer for materialization (EAPC-22385), local compute engine + Cassandra first. Off by default; gated behind the ENABLE_MATERIALIZATION_METRICS env var. - MaterializationMetricsAggregator (feast/_materialization_metrics.py): accumulates rows_read_offline, rows_written_online, drop_reasons, fields_written, field_null_counts, and max_event_timestamp/lag_seconds. Invariant: rows_read - rows_written == rows_dropped == sum(drop_reasons). - ExecutionContext carries an optional metrics_collector; instantiated in ComputeEngine.get_execution_context only for a MaterializationTask when the env gate is on. - Local nodes populate it: LocalSourceReadNode (rows_read), LocalFilterNode (filter drops), LocalDedupNode (dedup drops), LocalOutputNode (rows_written, fields, null counts, freshness). All no-ops when the collector is absent. - The online store reaches the aggregator via a ContextVar the output node binds around the write (collecting()), so online_write_batch's signature is unchanged. Cassandra records ttl_expired / ttl_exceeds_max at its TTL skip points, best-effort. - Unit tests for the aggregator and the node hooks, incl. the contextvar store-drop seam. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…olume metrics (EAPC-22385) Extend the write-time materialization metrics collector to the Spark compute engine and add the remaining Layer-1 volume metrics. - Spark path: MaterializationStatsAccumulatorParam merges per-executor stats (via the pure, commutative merge_stats) back to the driver; map_in_arrow builds a per-partition aggregator bound through collecting() so the online store's TTL-skip drops are captured on the executor. - merge_from_dict folds the accumulator result into the driver-side collector. - Volume metrics: bytes_written (Arrow nbytes, both engines) and distinct_entity_keys (exact via pyarrow group_by on the local engine; left unset on Spark to avoid a second DAG-re-executing pass -- HLL follow-up). - Layer-1 -> job bridge (record_run_result / drain_run_results) so the materialization job can drain write-time stats after store.materialize(). - Env-gated (ENABLE_MATERIALIZATION_METRICS), no-op when disabled. Tests: collector merge/volume/bridge + Spark accumulator path (pyspark-guarded). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…2385) - Type map_in_arrow's stats_accumulator as Accumulator (the runtime object returned by sparkContext.accumulator), not the AccumulatorParam merge-rule class -- AccumulatorParam has no .add(). - Assert getActiveSession() is not None before use in SparkWriteNode (a write node only runs against an active session), resolving the union-attr error. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Root cause of all-NULL Layer-1 fields (rows_read/written/dropped, fields_written,
field_null_counts, bytes, max_event_timestamp) on the Spark engine: the per-
executor tally was pushed into a Spark accumulator inside a mapInArrow UDF, and
accumulator updates from Arrow/pandas UDFs do not reliably propagate to the
driver (Spark wires accumulator updates through RDD actions, not the SQL/UDF
path). So stats_accumulator.value came back {} and merge_from_dict set nothing.
(The local engine tallies in-process on the driver, which is why it populated.)
Fix: map_in_arrow_online_stats does the same single-pass online write but RETURNS
one pickled MaterializationMetricsAggregator.to_dict() per partition as a binary
column; the driver .collect()s these and folds them with merge_stats -- a
returned result is guaranteed to reach the driver. Pickle preserves datetimes /
Counter / list fields. distinct_entity_keys stays unset on Spark (v1, unchanged).
Remove the now-dead accumulator machinery: MaterializationStatsAccumulatorParam,
the stats_accumulator plumbing in map_in_arrow (reverts it to a plain write
passthrough), and the unused imports.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The earlier Layer-1 work only instrumented SparkWriteNode (the DAG path, from_offline_store=False). Batch materialization actually runs SparkComputeEngine._materialize_from_offline_store (from_offline_store=True), which writes via map_in_pandas and had NO metrics capture -- so every Layer-1 field (rows_read/written/dropped, fields_written, field_null_counts, bytes, max_event_timestamp) was NULL regardless of the SparkWriteNode fix. Add map_in_pandas_online_stats: mirrors map_in_pandas' write exactly (incl. field mapping), tallies a MaterializationMetricsAggregator per partition, and RETURNS the pickled to_dict() in a binary column so the driver .collect()s and folds them with merge_stats (a returned result propagates; a Spark accumulator updated inside a pandas UDF does not). _materialize_from_offline_store now uses it (+ .collect()) when metrics are enabled, else the unchanged map_in_pandas path. Semantics: rows_written_online = rows submitted minus store-reported skips (the Cassandra store reports negative-/oversized-TTL skips as drops via collecting(), decrementing rows_written), so rows_read - rows_written == rows_dropped. This is a producer-side count, NOT an independent read-back verification (see follow-up). Best-effort: per-batch tally wrapped in try/except (never blocks the write); driver-side merge/record wrapped too. The .collect() write action is unguarded so real write failures still fail the job. distinct_entity_keys stays NULL on Spark (v1). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Which issue(s) this PR fixes:
Misc