boluor opened a new pull request, #3718:
URL: https://github.com/apache/doris-website/pull/3718

   ## Summary
   
   A pass of small correctness fixes across `docs/`, 
`versioned_docs/version-{2.1,3.x,4.x}/`, and the matching `i18n/zh-CN/` files.
   
   ### `sql-manual/.../view/SHOW-VIEW.md`
   
   - Replace the informal `grammar:` label with a proper `## Syntax` heading.
   - Drop the empty trailing `## Best Practice` section.
   
   ### `table-design/data-type.md` — DECIMAL row
   
   The cell mixed two bugs:
   
   - It closed the `<ul>` with another opening `<ul>` instead of `</ul>`, so 
the list never closed in HTML.
   - The third bullet read `When 16 < precision <= 38` (overlapping with the 
previous bullet). It should be `When 18 < precision <= 38`, matching the 
boundaries used in the `version-3.x` / `version-2.1` docs.
   
   Also close each `<li>` explicitly to match the corrected `</ul>`.
   
   ### `table-design/index/prefix-index.md`
   
   Frontmatter `keywords` listed `Prefix Index` and `Sort Key` twice each — 
dedupe.
   
   ### `table-design/index/ngram-bloomfilter-index.md`
   
   The example `SELECT` projects `any(product_title)`, but the result-table 
headers shown immediately below are `any_value(product_title)`. Rewrite the 
SELECT to `any_value(product_title)` so the displayed result actually matches 
the query a reader would copy.
   
   ### `table-design/index/inverted-index/custom-analyzer.md`
   
   - Strip a stray `</content></invoke>` block at the bottom of the file (looks 
like residue from a previous edit) — `version-4.x` and `current` were affected.
   - Dedupe `custom analyzer` in the frontmatter `keywords`.
   - Rename `min_ngram` / `max_ngram` to `min_gram` / `max_gram` in the 
parameter table and the bulleted parameter descriptions. Every working example 
in the same file, and the underlying tokenizer parameters Doris uses, are 
`min_gram` / `max_gram`.
   
   ### `table-design/index/vector-index/hnsw.md`
   
   The prose said _"…takes about 1.2x the memory…"_ while the formula on the 
very next line, and the example calculation that arrives at 650 MB, both use 
1.3x. Update the prose to 1.3x.
   
   ### `table-design/index/vector-index/ivf.md`
   
   For 128-dim / 1M rows, the formula above the table evaluates to "≈ 500 MB" 
while the reference-values table directly below says 496 MB. Align the table 
cell to 500 MB so the two presentations agree.
   
   ### `table-design/index/vector-index/overview.md`
   
   The Prepared Statement example used `FROM l2_distance_approximate` — that's 
the scalar function being projected, not a table. The intended table (used by 
all surrounding examples in this file) is `sift_1M`.
   
   ### `data-operate/import/data-source/bigquery.md`
   
   `https://cloud.google.com/bigquerydocs/exporting-data` is a 404. The correct 
path is `https://cloud.google.com/bigquery/docs/exporting-data`.
   
   ### `lakehouse/catalogs/jdbc-catalog-overview.md`
   
   The Maven Central example URL was given over plain HTTP 
(`http://repo1.maven.org/...`). `repo1.maven.org` redirects/enforces HTTPS, so 
the example fails as-shown — change to `https://`.
   
   ## Test plan
   
   - [x] Apply each substitution to the equivalent files in `docs/`, 
`versioned_docs/`, and `i18n/zh-CN/` where the same content exists.
   - [x] Spot-check rendered diffs for each finding.
   - [ ] CI build (docusaurus + sidebar checks).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to