Intended audience: Developers administrators
AO Platform: 5.0
Postman Collection
The repository includes a Postman v2.1 collection used to regression-test the OData layer against a sample ontology (paths and entity sets are aligned with the AO.UT schema used in platform scripts):
-
Collection File: OData-Calcite-Regression.postman_collection.json
-
Environment FileOData-Local.postman_environment.json
-
Typical environment variables:
platformServerUrl,basicAuthUser,basicAuthPassword, optionalxApiKey. Folder 18 also needsontologyUid(and optionallyontologyName) for raw MSO SQL APIs on the same host.
What it Covers
-
Core OData options: $filter, $compute, $expand, $search, $orderby (on declared properties), $top / $skip, $count, $apply aggregations, metadata/smoke checks, and nextLink preservation.
-
Geometry in JSON: When properties are exposed as Geometry in $metadata, responses use OData geospatial JSON; the collection includes $select / $expand cases for entity payloads (not the same as spatial predicates in $filter).
-
Not covered in OData $filter (current build): Canonical geo.distance, geo.length, and geo.intersects return 501 Not Implemented from the service. Spatial predicates that need ST_* should use raw semantic SQL (e.g. folder 18 —
getDataForMsoQuery/validateMsoQuery) or JDBC, not OData $filter. -
$orderby on $compute aliases (e.g.
$compute=... as mlen&$orderby=mlen desc) is not supported end-to-end; the collection expects 400 from the parser for that pattern.
Running with Newman
From the repo root (adjust paths if your clone layout differs):
newman run ao-platform/cloudseer-odata/postman/OData-Calcite-Regression.postman_collection.json -e ao-platform/cloudseer-odata/postman/OData-Local.postman_environment.json
Use an environment file that matches your server URL and credentials. The collection description field in Postman lists additional limitations and encoding notes (for example %2B for unary plus in query strings).
Contact App Orchid | Disclaimer