[vuanhphung]

Override native Thrift getFunctions() rows' FUNCTION_CAT with the original requested catalog, matching kernel and JDBC. Covers Arrow and column-based results, including prefetched data and omitted catalogs; other operations and empty-catalog validation are unchanged.

Adds 35 regression tests. All 1,349 unit tests pass with inherited agent markers cleared; library/test type-checks, targeted ESLint, Prettier, and diff checks pass. The standard type-check still fails on existing example self-imports. Live comparator not rerun.

---

This PR was created with GitHub MCP.

[peco-review-bot]

Verdict: 1 Low

Focused, well-tested fix — the undefined sentinel cleanly scopes the override to getFunctions, and the row === null guard preserves disableRowMaterialization placeholders correctly. One low-severity question: the override unconditionally rewrites FUNCTION_CAT on every row, forcing null for omitted catalogs and the literal pattern for wildcards, which the PR itself notes wasn't re-verified live.

[peco-review-bot]

🔵 Low — This overwrites FUNCTION_CAT on every returned row with the literal requested catalogName, including two cases that discard/mislabel server data:

• Omitted catalog (catalogName === undefined → functionCatalog === null): every row's FUNCTION_CAT is forced to null, throwing away the actual catalog names the server returned. A caller doing getFunctions({ functionName: '%' }) across all catalogs now loses that column entirely.
• Wildcard/pattern catalog (e.g. catalogName: '%'): every row is stamped with the literal string '%', which is not a real catalog name — so rows that legitimately span multiple catalogs are all mislabeled.

The tests assert exactly this behavior, so it is intentional and claimed to match JDBC/kernel — but JDBC's getFunctions catalog argument is an exact name (not a pattern), whereas the Thrift catalogName here can be a pattern. Since the PR notes the live comparator was not rerun, please confirm against a live warehouse that stamping null/pattern values (rather than passing rows through) is the intended parity behavior for the omitted-catalog and wildcard cases.

[github-actions]

Node.js integration tests triggered. View workflow runs. The result posts back here as the "Node.js Integration Tests" check.