sqon doc #1012
Merged
sqon doc #1012
Conversation
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
Contributor
Author
|
Consider outlining performance/functionality gain versus using simpler and more familiar postgres queries. |
joneubank
reviewed
Oct 14, 2025
joneubank
reviewed
Oct 14, 2025
Comment on lines
219
to
223
| | Operator | Description | Value Type | Example | | ||
| | -------- | ------------------------------------------------ | ------------------ | ------- | | ||
| | `"in"` | Field value must match one of the listed values | Array | `"value": ["Ontario", "Quebec"]` | | ||
| | `">="` | Field value must be greater than or equal to | Scalar (number) | `"value": 1640926800000` | | ||
| | `"<="` | Field value must be less than or equal to | Scalar (number) | `"value": 1672549199999` | |
Contributor
There was a problem hiding this comment.
This is a good start. Arranger can support more operators than this. We should definitely make a standardized absolute list and ensure compatibility across all services that use SQONs.
Member
There was a problem hiding this comment.
great idea! let's add this for now, and amend it later
3 tasks
Comment on lines
+148
to
+155
| | SQON Component | Elasticsearch Equivalent | Notes | | ||
| |----------------|-------------------------|-------| | ||
| | `"op": "and"` | `"bool": { "must": [...] }` | AND logic requires all conditions to match | | ||
| | `"op": "in"` | `"terms": { "field": [...] }` | IN operation uses Elasticsearch's `terms` query | | ||
| | `"fieldName": "data.primary_site"` | `"data.primary_site": [...]` | Field name maps directly to the index mapping | | ||
| | `"first": 20` | `"size": 20` | Pagination size parameter | | ||
| | `"offset": 0` | `"from": 0` | Pagination offset parameter | | ||
|
|
Member
There was a problem hiding this comment.
prettier generally does a good job at inserting spaces in md to make tables readable even without a md render. wonder if the settings in this repo need adjustment to make sure this tool is applied here
Co-authored-by: Anders Richardsson <2107110+justincorrigible@users.noreply.github.com>
Co-authored-by: Anders Richardsson <2107110+justincorrigible@users.noreply.github.com>
justincorrigible
approved these changes
Nov 18, 2025
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.
Remaining Tasks:
Netlify Page Preview: https://deploy-preview-33--overturedocs.netlify.app/docs/core-software/Arranger/usage/query-processing
Linked to this docs PR: overture-stack/docs#33
Note
Lyric also uses SQON, this should be documented within the Lyric documentation when it is completed