Doc/sql compatibility#14
Draft
dai-chen wants to merge 1 commit into
Draft
Conversation
dai-chen
commented
May 4, 2026
dai-chen
added a commit
that referenced
this pull request
May 4, 2026
Apply review feedback from PR #14: - Remove the 'document follows the structure of MySQL / PostgreSQL' reference paragraph from the Introduction. - Drop all in-body mentions of the analytics-engine (mustang) integration; the note simply states the unified SQL path is not enabled by default. - Mention 'Calcite' only once, in the Introduction. - Clarify LIMIT phrasing: it is a MySQL/PostgreSQL extension and not part of standard ANSI SQL (which uses OFFSET m ROWS FETCH FIRST n ROWS ONLY). - Fold the 'Named-argument syntax for search functions' bullet into the preceding 'Relevance search functions' bullet; the merged example now shows both positional and named-argument forms. - Remove the duplicate 'Lenient type coercion' and 'Backslash-escaped string literals' bullets from the Extensions section; both are deliberate deviations from standard SQL and remain documented in 'Differences from Standard SQL'. - Remove the 'ORDER BY NESTED()' row from Clause and syntactic differences; the NESTED() function is already covered under OpenSearch-specific functions. Signed-off-by: Chen Dai <daichen@amazon.com>
Add a user-facing SQL compatibility reference at docs/user/general/sql-compatibility.rst, modeled on MySQL's Standards Compliance and PostgreSQL's SQL Conformance pages. The new page covers: * SQL standards compliance (ANSI SQL-92 plus selected features from SQL:1999, SQL:2003, SQL:2008, and SQL:2016). * Extensions to standard SQL that the new engine accepts (hyphenated and backtick-quoted identifiers, GROUP BY by alias or ordinal, LIMIT N, optional FROM, relevance search functions). * Deliberate deviations from standard SQL, each driven by backward compatibility with OpenSearch SQL V2 (double-quoted strings, GROUP BY alias resolution, lenient type coercion, backslash escapes, MATCH as a non-reserved identifier). * A 'Migrating from SQL V2' chapter enumerating constructs that V2 accepted but the new engine rejects: lexical and literal differences, identifier differences, type-system differences, an extensive function-differences catalogue (~90 V2 functions grouped by purpose with standard SQL equivalents where one exists), clause and syntactic differences, metadata-statement differences, and output-format differences. Wire the new page into the Sphinx TOC under Language Structure. Signed-off-by: Chen Dai <daichen@amazon.com>
dai-chen
force-pushed
the
doc/sql-compatibility
branch
from
dc89743 to
d626331
Compare
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
1 participant
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.
Description
[Describe what this change achieves]
Related Issues
Resolves #[Issue number to be closed when this PR is merged]
Check List
--signoffor-s.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.