Repository navigation
Name every hand-written class of MobilitySpark in its README - #76
Merged
estebanzimanyi merged 1 commit intoOct 10, 2026
Merged
Conversation
The section of the README on how MobilitySpark is built names the hand-written classes of src/main. They are MeosMemory, which frees the native pointers MEOS returns, and the three classes of the package catalyst, which extend a Spark session: MobilitySparkExtensions registers the generated surface on every session and adds the optimizer rules OrderConjunctsByCost and MaterializeNestedLoopSides. None of them registers a function itself; the surface remains the generated one.
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.
The section of the README on how MobilitySpark is built names the hand-written classes of
src/main. They are MeosMemory, which frees the native pointers MEOS returns, and the three classes
of the package catalyst, which extend a Spark session: MobilitySparkExtensions registers the
generated surface on every session and adds the optimizer rules OrderConjunctsByCost and
MaterializeNestedLoopSides. None of them registers a function itself; the surface remains the
generated one.