Skip to content

[fix](sql-functions) provide setup data for the EXPORT_SET table example#3880

Merged
morningman merged 1 commit into
apache:masterfrom
boluor:fix/phantom-table-setup-export-set
Jun 3, 2026
Merged

[fix](sql-functions) provide setup data for the EXPORT_SET table example#3880
morningman merged 1 commit into
apache:masterfrom
boluor:fix/phantom-table-setup-export-set

Conversation

@boluor
Copy link
Copy Markdown
Contributor

@boluor boluor commented Jun 2, 2026

The EXPORT_SET page shows SELECT ... FROM test_export_set examples with an expected result, but never defines test_export_set. As written these examples cannot be run or reproduced — a reader who copies them gets Table [...] does not exist.

This PR adds the missing CREATE TABLE + INSERT, carried in a standard HTML comment (<!-- setup-sql ... -->) just before the example. Because it is an HTML comment, the rendered page is unchanged and no documented expected output is modified.

The table contents were reverse-derived from the printed input table and verified end-to-end on version-4.x (a 4.1.1 cluster) and dev/current (a master build): both the input table and the EXPORT_SET(...) results match the documented output exactly, including the row whose separator is the literal |123|.

The page exists only in the dev/current and version-4.x trees; updated in EN + ZH (4 files). No ja-source changes.

Note: a separate, pre-existing inconsistency on this page — one example whose SQL selects a single column while its output table shows six (bits | on | off | sep | num_of_b | ans) — is not addressed here; it is tracked in #3879 so the SQL/output correction can be reviewed on its own.

The EXPORT_SET page shows `SELECT ... FROM test_export_set` examples with an
expected result, but never defines `test_export_set`, so the examples cannot be
run or reproduced ("table does not exist").

Add the missing CREATE TABLE + INSERT, carried in a standard HTML comment
(`<!-- setup-sql ... -->`) before the example. As an HTML comment it does not
change the rendered page, and no documented expected output is modified.

The table contents were reverse-derived from the printed input table and verified
end-to-end on version-4.x (4.1.1) and dev/current (master): the input table and the
EXPORT_SET results match the documented output exactly, including the row whose
separator is the literal "|123|".

Updated in EN + ZH across dev/current and version-4.x (the page exists only in
those two trees).

Note: a separate, pre-existing inconsistency on this page (one example's SQL selects
one column while its output table shows six) is tracked in apache#3879 and intentionally
left out of this setup-only change.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@morningman morningman merged commit 0afc024 into apache:master Jun 3, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants