Downstream dialect allowlists don't recognize OSSIE_SQL_2026
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
Research direction
Read the five affected locations listed in the issue, starting with the allowlists and fallback chains in the Orionbelt, Snowflake, Databricks, and Wisdom converters, then review validation/validate.py's DIALECT_MAP and SKIP_SQL_VALIDATION. Add regression tests for fields or metrics expressed only in OSSIE_SQL_2026 in each affected component. Done means those values are retained or handled without misleading warnings, and validation maps the dialect explicitly.
Written by the indexing model from the issue text.
Description
Background
apache/ossie#439 added OSSIE_SQL_2026 as a dialect in the core spec, and apache/ossie#440 added the matching value to the Python OssieDialect enum. Documents using OSSIE_SQL_2026 now pass model validation, but several downstream components hard-code dialect allowlists that predate this dialect and don't recognize it. As a result, fields/metrics expressed only in OSSIE_SQL_2026 are silently dropped or produce misleading warnings, even though the dialect is ANSI-SQL-compatible.
Affected locations
converters/orionbelt/src/ossie_orionbelt/_common.py:41—_SQL_PARSEABLE_DIALECTStuple omitsOSSIE_SQL_2026, so_select_sql_expression()drops such metrics from OBML export with a "no SQL-parseable dialect" warning.converters/snowflake/src/ossie_snowflake/converter.py:372—_extract_expression()only recognizesSNOWFLAKE/ANSI_SQL, so matching fields/metrics are skipped from Snowflake export with a misleading warning.converters/databricks/src/ossie_databricks/_common.py:231—pick_expression()only falls back throughDATABRICKS/ANSI_SQL, returningNoneand causing the field/metric to be dropped from Databricks Metric View output.converters/wisdom/src/ossie_wisdom/ossie_to_wisdom.py:148—_infer_dataset_dialect()/_pick_expression()never checkOSSIE_SQL_2026, producing a spuriousMISSING_DIALECT_EXPRESSIONissue even though a fallback expression is still used.validation/validate.py:67—DIALECT_MAP/SKIP_SQL_VALIDATIONomitOSSIE_SQL_2026; it currently validates correctly only by accident, becausedict.get()'s default happens to match the sameNonesentinel used forANSI_SQL. This should be made an explicit mapping rather than relying on that coincidence.
Suggested fix
Treat OSSIE_SQL_2026 as ANSI-SQL-compatible in each of the allowlists/fallback chains above (mirroring how ANSI_SQL is handled), and add regression tests per converter covering a field/metric expressed only in OSSIE_SQL_2026.
Related
Follow-up from review of apache/ossie#440.
- Dominant language
- Python
- Stars
- 45
- Forks
- 53
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 100
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/ossie-converters
-
[dbt] exported dataset keys reference physical columnsPossibly taken @WilliamKelley claimed this today. Openneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/ossie-converters#251 ·
Maintainers usually reply within 2 days
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/ossie-converters#195 ·
Maintainers usually reply within 2 days
-
Sigma converter: SumIf emits ELSE 0, so empty matches return 0 instead of NULLMay be free again A pull request for this issue was closed without being merged. Openconverter/sigma
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
apache/ossie-converters#20 · 1 comment ·
Maintainers usually reply within 2 days
-
[dbt] exported relationship columns reference physical columnsPossibly taken @WilliamKelley claimed this today. Openneeds-triage
Difficulty 3/5 1-2 days Newbie friendliness 64/100
apache/ossie-converters#253 ·
Maintainers usually reply within 2 days
-
needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
apache/ossie-converters#243 · 1 comment ·
Maintainers usually reply within 2 days
All issues in apache/ossie-converters
Similar issues
-
LLMContextNode tool builders fail on nested params like `params:retrieval.max_matches`Possibly taken @Shizoqua claimed this today. OpenCommunity
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
btclib-org/portanode#985 ·
Maintainers usually reply within 1 day
-
[Bug]: maps skill OSRM foot/cycling returns car times (router.project-osrm.org ignores profile)Opencomp/tools P2 tool/skills type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#158494 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
needs-format
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Niko1221/Strata#6475 · 1 comment ·
Maintainers usually reply within 6 days