Repository navigation
test: port legacy reader workloads to the modern generator - #62
Merged
Merged
Conversation
rliao147
requested review from
OussamaSaoudi
and removed request for
OussamaSaoudi
September 26, 2026 00:21
rliao147
force-pushed
the
stack/port-legacy-dat-tests
branch
from
September 26, 2026 00:51
6fd294d to
deca116
Compare
OussamaSaoudi
approved these changes
Sep 28, 2026
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
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.
Description
This change retires the legacy Python DAT reader generator and use the modern Scala workload generator as the source of public DAT workloads. Most legacy scenarios were already covered by modern suites. This adds the missing checkpoint and protocol workloads:
The legacy Python generator, PySpark reader test, Python-only dependencies, and obsolete CI commands are removed.
How was this patch tested?
Self-validation for all newly added workloads
Does this require an update to the documentation?
No