docs: record geoQ notification-filter verification result - #148
Merged
Conversation
The layer 3 checklist flagged q/geoQ notification filtering as an open question to record per broker. Recorded the GeonicDB result from the 2026-08-05 live round trip on plugin 3.3.0: geoQ is enforced on notifications when sent in NGSI-LD syntax; the earlier observation that it was ignored came from the pre-3.3.0 NGSIv2-syntax payloads. The q filter remains accepted but not applied there.
There was a problem hiding this comment.
Pull request overview
Updates the Layer 3 (NGSI-LD round trip) release verification checklist to record the observed behavior of q/geoQ notification filtering for GeonicDB, based on a live test run on 2026-08-05 with plugin 3.3.0.
Changes:
- Rewords the existing “upstream gap” note into “filter enforcement varies by broker”.
- Documents the verified GeonicDB results:
geoQworks for notifications when using NGSI-LD syntax;qis accepted but not enforced for notifications. - Captures the root cause of earlier
geoQfailures as NGSIv2-style payloads accepted but never matchable.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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 layer 3 (NGSI-LD round trip) checklist in
doc/release_verification.mdlistedq/geoQnotification filtering as an open question, with an instruction to run the three-phase test and record the result per broker.This records the result from a live round trip against GeonicDB on 2026-08-05 with plugin 3.3.0:
geoQis applied to notifications when the subscription carries NGSI-LD syntax (withinwith a GeoJSON polygon in lon,lat order). An entity inside the polygon produced exactly one notification and issue; one far outside produced none, and the subscription'stimesSentstayed at 1.geoQignored were caused by the pre-3.3.0 payloads in NGSIv2 syntax, which the broker accepted on the subscription but could never match.qgap is real on that broker: accepted on subscriptions, not applied to notifications.Documentation only, no code changes.