Skip to content

Name every hand-written class of MobilitySpark in its README #76

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
estebanzimanyi merged 1 commit into from
Oct 10, 2026
Merged

Name every hand-written class of MobilitySpark in its README #76

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,8 +42,13 @@ MobilityDB (master)
The generator is `tools/codegen_jvm.py --engine spark`, which **JMEOS owns**. This repository
stages it: `tools/codegen_jvm.py`, `tools/codegen_spark_udfs.py` and `tools/meos-idl.json` are
gitignored, and the refresh chain and CI copy them in. Nothing under `target/generated-sources`
is committed either. The one hand-written class in `src/main` is `MeosMemory`, which frees the
native pointers MEOS returns.
is committed either. The hand-written classes in `src/main` register no function themselves:
`MeosMemory` frees the native pointers MEOS returns, and the three classes of the package
`catalyst` extend a Spark session: `MobilitySparkExtensions`, named in `spark.sql.extensions`,
registers the generated surface on every session and adds the two optimizer rules
`OrderConjunctsByCost`, which evaluates a conjunct calling a user-defined function after the
conjuncts that do not, and `MaterializeNestedLoopSides`, which computes once each side of a
nested-loop join that calls one.

`GENERATION.md` is the full contract.

Expand Down
Loading