Skip to content

docs: record geoQ notification-filter verification result #148

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
dkastl merged 2 commits into from
Aug 5, 2026
Merged

docs: record geoQ notification-filter verification result #148

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7286569
docs: record geoQ notification-filter verification result
dkastl Aug 5, 2026
e75ff60
docs: apply review grammar fixes
dkastl Aug 5, 2026
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
16 changes: 13 additions & 3 deletions doc/release_verification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,9 +116,19 @@ Same shape as layer 2 against an NGSI-LD broker (hosted or local). Watch for:
- broker callbacks need a publicly reachable Redmine URL (a
`cloudflared tunnel --url http://127.0.0.1:3000` quick tunnel works; Rails
host authorization must allow the tunnel host in development)
- **known upstream gap:** some brokers accept `q`/`geoQ` on subscriptions but
do not apply them to notifications — run the layer 2 three-phase test here
too and record the result
- **filter enforcement varies by broker:** some brokers accept `q`/`geoQ` on
subscriptions but do not apply them to notifications. Run the layer 2
three-phase test here too and record the result. Recorded for GeonicDB
(2026-08-05, plugin 3.3.0): `geoQ` is applied to notifications when sent in
NGSI-LD syntax (`within` with a GeoJSON polygon in lon, lat order); an
entity inside the polygon produced exactly one notification and one entity
far outside produced none, with the subscription's `timesSent` staying at
1. Earlier
runs that saw `geoQ` ignored were caused by the pre-3.3.0 payloads in
NGSIv2 syntax, which the broker accepted on the subscription but could
never match. The `q` gap is real on GeonicDB: accepted on subscriptions,
not applied to notifications, so `watchedAttributes` and `geoQ` are the
filters that take effect there

## Cleanup

Expand Down
Loading