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

   ## Summary
   
   The \`array-count\` page on EN current/dev and version-4.x contained an 
example referencing \`array_length(x)\`, which is not a registered function in 
Doris. Verified in 
[\`fe/fe-core/.../BuiltinScalarFunctions.java#L703\`](https://github.com/apache/doris/blob/master/fe/fe-core/src/main/java/org/apache/doris/catalog/BuiltinScalarFunctions.java#L703):
   
   \`\`\`java
   scalar(Cardinality.class, \"array_size\", \"cardinality\", \"size\"),
   \`\`\`
   
   \`array_size\` is the canonical name; \`cardinality\` and \`size\` are 
aliases. \`array_length\` was never registered, so the example as written would 
fail at analysis time with \"unknown function\". Verified identical on 
\`branch-3.1\`, \`branch-4.0\`, \`branch-4.1\`, and \`master\`.
   
   ## Scope
   
   Two EN files (zh and 3.x/2.1 versions don't carry this example block):
   - 
\`docs/sql-manual/sql-functions/scalar-functions/array-functions/array-count.md\`
   - 
\`versioned_docs/version-4.x/sql-manual/sql-functions/scalar-functions/array-functions/array-count.md\`
   
   Changes per file (lines 160-165 of the affected block):
   - \`array_length(x)\` → \`array_size(x)\` in the SQL and the column header
   - Re-flow the result-table borders from 50 dashes to 64 to match the actual 
62-character column-header width (the existing borders were already too narrow 
to contain the header — a separate pre-existing formatting bug fixed in passing)
   
   ## Test plan
   
   - [x] Source-of-truth verified across all maintained release branches (3.1, 
4.0, 4.1, master) — \`array_length\` is not registered anywhere
   - [x] Dead-link check passes
   - [x] Output table borders now align with column-header width


-- 
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