[SPARK-48543][SS] Track state row validation failures using explicit error class

[anishshri-db]

What changes were proposed in this pull request?

Track state row validation failures using explicit error class

Why are the changes needed?

We want to track these exceptions explicitly since they could be indicative of underlying corruptions/data loss scenarios.

Does this PR introduce any user-facing change?

No

How was this patch tested?

Existing unit tests

13:06:32.803 INFO org.apache.spark.util.ShutdownHookManager: Deleting directory /Users/anish.shrigondekar/spark/spark/target/tmp/spark-6d90d3f3-0f37-48b8-8506-a8cdee3d25d7
[info] Run completed in 9 seconds, 861 milliseconds.
[info] Total number of tests run: 4
[info] Suites: completed 1, aborted 0
[info] Tests: succeeded 4, failed 0, canceled 0, ignored 0, pending 0
[info] All tests passed.

Was this patch authored or co-authored using generative AI tooling?

No

[anishshri-db]

cc - @HeartSaVioR - PTAL, thx !

[anishshri-db]

Tests are all passing. Not sure why the page is not updated.

[HeartSaVioR]

+1

[HeartSaVioR]

Wait... @anishshri-db if we consider this as worth monitoring, is it sufficient that we categorize this as internal class with state store? Wouldn't we like to give an explicit error class instead?

[anishshri-db]

@HeartSaVioR - PTAL now, thx !

[HeartSaVioR]

Only one minor. Thanks for making change!

[HeartSaVioR]

+1 pending CI

[HeartSaVioR]

Thanks! Merging to master.