…ANT slots in scan copies

### What problem does this PR solve?

Issue Number: None

Related PR: apache#69292, apache#69399

Problem Summary:

Review of 8fc7d7c found two problems:

- A minimum score under GROUPING SETS, ROLLUP or CUBE, e.g.
  SELECT c2, count(*) FROM t WHERE c1 MATCH 'apple' AND score() > 0.00001
  GROUP BY GROUPING SETS ((c2), ()), was rejected as an unsupported SELECT:
  the binder did not walk through the LogicalRepeat that analysis puts below
  the aggregate. It now does, so the minimum score works as with any other
  GROUP BY, and score() in the select list of such a SELECT gets the
  aggregate error.
- The plan copier computed the output of a copied scan again after replacing
  its virtual columns. That gives VARIANT subpath slots new ids, which the
  copier had already mapped, so a CTE that reads v['x'] and has a MATCH in
  its select list failed with "A expression contains slot not from children"
  when the optimizer inlined it. The copier fix is now the one of apache#69399:
  LogicalOlapScan.withVirtualColumns replaces the slots of the old virtual
  columns in the output and keeps the other slots, and the copier no longer
  computes the output again. This PR carries the same change until apache#69399 is
  merged.

### Release note

None

### Check List (For Author)

- Test: Unit Test and Regression test
    - BindScoreToOlapScanTest: GROUPING SETS, ROLLUP and CUBE with a minimum
      score, and max(score()) with ROLLUP; all 73 tests pass. The copier
      tests are the ones of apache#69399, whose CTEInlineTest covers the VARIANT
      case. LogicalPlanDeepCopierTest, SearchCteRewriteTest,
      PushDownVirtualColumnsIntoOlapScanTest, PhysicalPlanTranslatorTest,
      PushDownMatchProjectionAsVirtualColumnTest, CTEInlineTest,
      LogicalOlapScanTest and SearchExpressionTest pass (157 tests with
      BindScoreToOlapScanTest). Checkstyle passes.
    - Regression tests: test_score_filter_usage gets a GROUPING SETS case,
      with its .out regenerated by the framework. The 19 suites that use
      score() pass on a private cluster.
- Behavior changed: Yes. A minimum score is supported with GROUPING SETS,
  ROLLUP and CUBE.
- Does this need documentation: No

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…pache#69399

### What problem does this PR solve?

Issue Number: None

Related PR: apache#69292, apache#69399

Problem Summary:

Review of apache#69399 found that the plan copier still mishandled virtual
columns that refer to each other, which CSE creates with
experimental_enable_virtual_slot_for_cse=true: copying them in list order
kept the old id of a virtual column that comes later in the list. apache#69399 now
maps every virtual column to its new id before copying their expressions.
This PR carries the identical change until apache#69399 is merged.

### Release note

None

### Check List (For Author)

- Test: Unit Test
    - LogicalPlanDeepCopierTest, with the new test for virtual columns that
      refer to each other, BindScoreToOlapScanTest, SearchCteRewriteTest,
      PushDownVirtualColumnsIntoOlapScanTest, PhysicalPlanTranslatorTest,
      PushDownMatchProjectionAsVirtualColumnTest, CTEInlineTest,
      LogicalOlapScanTest and SearchExpressionTest pass. Checkstyle passes.
      The regression suites were not run again: they create no virtual
      columns that refer to each other.
- Behavior changed: No
- Does this need documentation: No

Co-Authored-By: Claude Opus 5.5 <[email protected]>

### What problem does this PR solve?

Issue Number: None

Related PR: apache#69292, apache#69399

Problem Summary:

apache#69399, the plan copier fix that this PR carried until it was merged, is now
on master. Merge master so that the copier change leaves the diff of this
PR.

### Release note

None

### Check List (For Author)

- Test: Unit Test (the FE tests around the copier and the binder are run
  after the merge)
- Behavior changed: No
- Does this need documentation: No

Co-Authored-By: Claude Opus 5.5 <[email protected]>

… in scan expressions

### What problem does this PR solve?

Issue Number: None

Related PR: apache#69399, apache#69419

Problem Summary:

The score() support of this PR special-cased generic code: TopN filter
pushdown skipped scans with a score, the MV rewrite check skipped them,
and the rewrite-time binder recognized the delete sign filter of UNIQUE
tables and rejected table streams by class. All of it came from one BE
limitation and from binding score() after analysis.

BE: the olap scan prepares the score of every row of its row bitmap
before the first batch, but SegmentIterator marked only the stored
columns of a pushed-down expression as common-expression columns. An
expression on the score alone, e.g. score() > 0.5, set no
_is_need_expr_eval, so it was never evaluated, while the scanner had
already removed it from its own conjuncts. An expression that read the
score next to other columns, e.g. a TopN filter on CAST(score() AS INT),
evaluated Score() itself, which returns 0. SegmentIterator now marks the
score column like a stored column: it is read with the other
common-expression columns, before the expressions run.

FE, analysis: BindScore replaces BindScoreToOlapScan. It runs first on
each plan the analyzer binds (a statement, and on their own its views,
CTEs and subqueries), while the plan nodes of a SELECT are still its
clauses, so it needs no knowledge of what analysis adds later. For each
SELECT that calls score(), it checks the usage rules, asks the table in
its FROM clause for a score column and replaces the score() calls with
that column. BindRelation adds the column to the olap scan and rejects a
relation that cannot provide it, e.g. a view, a CTE or a table stream.
The column is left out of *. CheckScoreInCorrelatedSubquery rejects a
scored scan under a correlated subquery after SubqueryToApply. Since
score() no longer reaches type coercion as a function, the check that it
is compared with numbers moves from ComparisonPredicate to BindScore,
which sees the type of a literal before binding.

FE, rewrite: the minimum score is an ordinary predicate of the scan.
PushDownScoreRangeIntoOlapScan is removed; PushDownScoreTopNIntoOlapScan
moves the minimum into the scan together with a TopN on the score, as on
master, because the scan keeps the best rows of a segment only when no
predicate follows. TopnFilterPushDownVisitor, the MV check and the
translator lose their score() cases: a TopN filter reads the score like
any column, and a materialized view without the score cannot answer a
predicate on it.

### Release note

None

### Check List (For Author)

- Test: Unit Test and Regression test
    - BE: SegmentIteratorScoreCommonExprTest is new. With
      SegmentIteratorApplyIndexExprTest and
      SegmentIteratorCandidatePushdownTest, 35 tests pass.
    - FE: BindScoreTest (79 tests), the tests of nereids/rules/analysis,
      CTEInlineTest, LogicalPlanDeepCopierTest, TopNRuntimeFilterTest,
      PullUpProjectExprUnderTopNTest and MaterializedViewUtilsTest pass.
      Checkstyle passes.
    - Regression: the 20 suites that use score() (inverted_index_p0,
      search, ann_index_p0, nereids_rules_p0/cte) pass on an ASAN build
      of this commit. Their .out files are unchanged; two suites check
      the new EXPLAIN output.
- Behavior changed: Yes. TopN filters on keys computed from score() reach
  the scan. Without a TopN on the score, EXPLAIN shows the minimum score
  among the scan predicates instead of SCORE RANGE.
- Does this need documentation: No

Co-Authored-By: Claude Opus 5.5 <[email protected]>

### What problem does this PR solve?

Issue Number: N/A

Related PR: #69399 (merged; the plan copier fix this PR needs), #69419
(merged; fixes the pre-existing MATCH predicate inference that review of
this PR found)

Problem Summary:

`score()` only worked as `ORDER BY score() LIMIT n` directly above the
scan whose MATCH defines it. A minimum score filter without that TopN
evaluated the unbound `score()` placeholder as zero and silently dropped
every row:

```sql
SELECT id FROM documents
WHERE content MATCH 'apple' AND score() > 0.00001;  -- returned nothing
```

`score()` is computed by the olap scan that evaluates the MATCH and
SEARCH predicates of its SELECT. This PR binds `score()` to that scan at
the start of rewrite, makes the scan's expressions read the score, and
rejects every other use with an error that names the rule.

**Supported.** A SELECT that reads one table and has a MATCH or SEARCH
predicate in its WHERE clause can use `score()`:
- in the WHERE clause, as one minimum score: `score() > x` or `score()
>= x` (also `x < score()`, `x <= score()`, and with a FLOAT or DOUBLE
cast);
- in the select list, window functions and ORDER BY, if the SELECT does
not aggregate (with GROUP BY, including GROUPING SETS, ROLLUP and CUBE,
aggregate functions or DISTINCT, `score()` can only be the minimum
score).

A scored SELECT in a subquery, view, CTE or set operation still needs
`ORDER BY score() LIMIT n`, as before. The TopN keeps the predicates of
the outer query out of its scan, e.g. an outer MATCH cannot add to its
score. A correlated subquery cannot call `score()`, because
decorrelation removes that TopN.

**Rejected.** A join, a subquery or a lateral view in the scored SELECT;
a view, CTE or other relation that is not an olap table (a table stream
fails during planning, because its scan is replaced by scans of the
table and of its changes); any other filter on the score (`score() < x`,
`score() = x`, lossy casts, ORs, a second bound); `score()` in
aggregates, GROUP BY, HAVING or QUALIFY; MATCH or SEARCH in HAVING or
QUALIFY of a scored SELECT, also through an alias; `score()` in a
correlated subquery; a SELECT without its own MATCH or SEARCH; a nested
scored SELECT without the TopN.

**How.**
- BE: the scan reads the score in its own expressions. `SegmentIterator`
prepares the score of every row of its row bitmap before the first
batch. It marked only stored columns of a pushed-down expression as
common-expression columns, so an expression on the score alone, e.g.
`score() > 0.5`, was never evaluated (and the scanner had already
removed it from its conjuncts), and an expression that read the score
next to other columns, e.g. a TopN filter on `CAST(score() AS INT)`,
evaluated `Score()` itself, which returns 0. Now the score column is
read with the other common-expression columns, before the expressions
run.
- FE, binding: `BindScoreToOlapScan` replaces `CheckScoreUsage`. It runs
first in rewrite, while subqueries, views and CTEs still have their own
plan nodes, so the analysis classes are as on master. For each SELECT
that calls `score()`, it checks the rules above, adds a score column to
the scan (score limit 0: the scan scores every row it returns) and
replaces the `score()` calls of the SELECT with that column. A table is
a relation, also under the filters analysis puts on it (the delete sign
filter of a UNIQUE table, row policies). Binding after analysis also
covers `* REPLACE (score() AS c)`, alias functions over `score()` and
`ORDER BY` a position, and a UDF named `score` is never mistaken for it.
- FE, rewrite: the minimum score is an ordinary predicate of the scan.
`PushDownScoreTopNIntoOlapScan` pushes a TopN on the score into the
scan, and with it the minimum score, exactly as before this PR (with a
zero score limit when SEARCH has another predicate), because the scan
keeps the best rows of a segment only when no predicate follows. TopN
filter pushdown and MV rewrite need no `score()` cases: a TopN filter
reads the score like any other column, and a materialized view without
the score cannot answer a predicate on it.
- This PR needs the plan copier fix of #69399, which is merged: copying
a scan with virtual columns gave each one two ids and kept the old slot
in the output.
- The BE keeps the score unchanged by MATCH projections:
`SegmentIterator` evaluates them without the score collector.
- `SearchExpression` can be rendered as SQL, which the shape plan logged
at debug level and `EXPLAIN SHAPE PLAN` need.

### Release note

`score()` works in the select list, window functions and ORDER BY of a
SELECT on one table whose WHERE clause has MATCH or SEARCH, with an
optional minimum score `score() > x` or `score() >= x`, without `ORDER
BY score() LIMIT`. A scored SELECT in a subquery, view, CTE or set
operation still needs `ORDER BY score() LIMIT`. Other uses of `score()`
are rejected instead of evaluating it as 0.

…#69399 (#69560)

### What problem does this PR solve?

Related PR: #69399

Problem Summary: Backport #69399 to `branch-4.2`.

A CTE fails to plan with "A expression contains slot not from children"
when the optimizer inlines it after one of its scans got a virtual
column: a CTE that orders by `score()` or by an ANN distance with a
LIMIT, or that has MATCH in its select list and is inlined after
rewrite. `LogicalPlanDeepCopier` gave each virtual column two ids,
copied them in list order, kept the old slot in the output of the copied
scan and left the score and ANN order keys on the old slots. The copier
now maps every virtual column to its new id before copying their
expressions and remaps the order keys, and
`LogicalOlapScan.withVirtualColumns` replaces the old virtual slots in
the output.

#### Branch adaptations

The branch has no table streams, so the change to
`LogicalOlapTableStreamScan` is dropped. `withVirtualColumns` keeps the
constructor call of the branch, `LogicalPlanDeepCopier` imports
`LogicalOlapScan`, which master already imported, and
`LogicalPlanDeepCopierTest` keeps the tests of the branch and adds the
two tests of #69399.

### Release note

Fix "A expression contains slot not from children" for a CTE that orders
by `score()` or by an ANN distance with a LIMIT, or that has MATCH in
its select list and is inlined after rewrite.

### Check List (For Author)

- Test
    - [x] Regression test
    - [x] Unit Test
    - [ ] Manual test
- Behavior changed:
    - [x] No.
- Does this need documentation?
    - [x] No.

### Validation

Validated together with the other two backports (#69399, #69419 and
#69292 on `branch-4.2` at ecbc5fe), in a local ASAN build:

- PASS: FE unit tests `LogicalPlanDeepCopierTest`, `CTEInlineTest`,
`InferPredicateByReplaceTest`, `InferPredicatesTest`,
`UnequalPredicateInferTest`, `BindScoreToOlapScanTest`,
`SearchExpressionTest`, `TopNRuntimeFilterTest`,
`PullUpProjectExprUnderTopNTest` and `MaterializedViewUtilsTest` (280
tests), and FE Checkstyle.
- PASS: `./build.sh --fe --be`.
- PASS: BE unit tests `SegmentIteratorScoreCommonExprTest`,
`SegmentIteratorApplyIndexExprTest` and `VirtualSlotRefTest` (31 tests);
clang-format 16 on the changed BE files.
- PASS: the 23 regression suites of the branch that use `score()`,
including `test_cte_inline_virtual_column`, `infer_match_predicate`,
`test_score_filter_usage` and `test_score_filter_matrix`, with unchanged
`.out` files.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <[email protected]>

…69292 (#69562)

### What problem does this PR solve?

Related PR: #69292

Problem Summary: Backport #69292 to `branch-4.2`. It contains the commit
of #69560, the backport of #69399, which it needs: binding runs before
CTE inlining, which copies scans with virtual columns. Merge #69560
first.

`score()` only worked as `ORDER BY score() LIMIT n` directly above the
scan whose MATCH defines it. A minimum score filter without that TopN
evaluated the unbound `score()` placeholder as zero and silently dropped
every row:

```sql
SELECT id FROM documents WHERE content MATCH 'apple' AND score() > 0.00001;  -- returned nothing
```

`BindScoreToOlapScan`, which replaces `CheckScoreUsage`, binds `score()`
to the scan of its SELECT at the start of rewrite and rejects the uses
it cannot bind. The minimum score stays a predicate of the scan, and
`PushDownScoreTopNIntoOlapScan` still pushes a TopN on the score
together with the minimum. In the BE, an expression on the score reads
the score column instead of evaluating `Score()`, and MATCH projections
do not add to the score. See #69292 for the supported and rejected uses.

#### Branch adaptations

- The `SegmentIterator` of the branch collects the columns of
pushed-down expressions in `_extract_common_expr_columns` instead of
per-column states, so the score column is marked there, and the new BE
test checks `_common_expr_columns` and `_is_common_expr_column`. The
branch reads the columns collected there before it evaluates the
expressions, also virtual ones, and a virtual slot uses a column that is
already read.
- When `limit + offset` overflows, `PushDownScoreTopNIntoOlapScan` keeps
the behavior of the branch and skips the push-down instead of failing.
- `SearchDslParser` is imported from its package on the branch.
- The branch does not have #68672, which keeps predicates on virtual
columns out of the condition cache. The minimum score is now a predicate
of the scan, and a score depends on every rowset, so a cached result
goes stale when a rowset is added: without the change,
`test_score_filter_matrix` lost the rows of the first rowset.
`VirtualSlotRef::get_digest` returns 0 as on master, the part of #68672
that this needs, with the `VirtualSlotRef` tests of #68672 that the
branch can run.

### Release note

`score()` works in the select list, window functions and ORDER BY of a
SELECT on one table whose WHERE clause has MATCH or SEARCH, with an
optional minimum score `score() > x` or `score() >= x`, without `ORDER
BY score() LIMIT`. A scored SELECT in a subquery, view, CTE or set
operation still needs `ORDER BY score() LIMIT`. Other uses of `score()`
are rejected instead of evaluating it as 0.

### Check List (For Author)

- Test
    - [x] Regression test
    - [x] Unit Test
    - [ ] Manual test
- Behavior changed:
- [x] Yes. A minimum score works without `ORDER BY score() LIMIT`, and
unsupported uses of `score()` fail planning instead of evaluating it as
0. A minimum score without a TopN needs the BE change, so BEs must be
upgraded before FEs.
- Does this need documentation?
- [x] Yes. The `score()` documentation should describe where `score()`
can be used.

### Validation

Validated together with the other two backports (#69399, #69419 and
#69292 on `branch-4.2` at ecbc5fe), in a local ASAN build:

- PASS: FE unit tests `LogicalPlanDeepCopierTest`, `CTEInlineTest`,
`InferPredicateByReplaceTest`, `InferPredicatesTest`,
`UnequalPredicateInferTest`, `BindScoreToOlapScanTest`,
`SearchExpressionTest`, `TopNRuntimeFilterTest`,
`PullUpProjectExprUnderTopNTest` and `MaterializedViewUtilsTest` (280
tests), and FE Checkstyle.
- PASS: `./build.sh --fe --be`.
- PASS: BE unit tests `SegmentIteratorScoreCommonExprTest`,
`SegmentIteratorApplyIndexExprTest` and `VirtualSlotRefTest` (31 tests);
clang-format 16 on the changed BE files.
- PASS: the 23 regression suites of the branch that use `score()`,
including `test_cte_inline_virtual_column`, `infer_match_predicate`,
`test_score_filter_usage` and `test_score_filter_matrix`, with unchanged
`.out` files.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <[email protected]>

…cross column equalities #69419 (#69561)

### What problem does this PR solve?

Related PR: #69419

Problem Summary: Backport #69419 to `branch-4.2`.

Predicate inference copied a predicate on one column to every column
that is equal to it, also when the predicate contained MATCH,
multi_match or SEARCH. Their result depends on the inverted index of the
column, not only on its value: with `c1 = c2` and different parsers on
the two columns, the copy removed matching rows, and with the same index
it doubled `score()`, so a minimum score let low-scored rows through.
`InferPredicateByReplace.infer` now skips every input that contains
`Match`, `MultiMatch`, `Search` or `SearchExpression`.

#### Branch adaptations

The branch does not have the `NoneMovableFunction` check that master has
next to the new check, so only the new check is added. The test imports
`SearchDslParser` from its package on the branch.

### Release note

Fix wrong results and scores when predicate inference copied a MATCH,
multi_match or SEARCH predicate to an equal column.

### Check List (For Author)

- Test
    - [x] Regression test
    - [x] Unit Test
    - [ ] Manual test
- Behavior changed:
- [x] Yes. Predicate inference no longer copies a predicate that
contains MATCH, multi_match or SEARCH to an equal column.
- Does this need documentation?
    - [x] No.

### Validation

Validated together with the other two backports (#69399, #69419 and
#69292 on `branch-4.2` at ecbc5fe), in a local ASAN build:

- PASS: FE unit tests `LogicalPlanDeepCopierTest`, `CTEInlineTest`,
`InferPredicateByReplaceTest`, `InferPredicatesTest`,
`UnequalPredicateInferTest`, `BindScoreToOlapScanTest`,
`SearchExpressionTest`, `TopNRuntimeFilterTest`,
`PullUpProjectExprUnderTopNTest` and `MaterializedViewUtilsTest` (280
tests), and FE Checkstyle.
- PASS: `./build.sh --fe --be`.
- PASS: BE unit tests `SegmentIteratorScoreCommonExprTest`,
`SegmentIteratorApplyIndexExprTest` and `VirtualSlotRefTest` (31 tests);
clang-format 16 on the changed BE files.
- PASS: the 23 regression suites of the branch that use `score()`,
including `test_cte_inline_virtual_column`, `infer_match_predicate`,
`test_score_filter_usage` and `test_score_filter_matrix`, with unchanged
`.out` files.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <[email protected]>

### What problem does this PR solve?

Related PR: apache#69399

Problem Summary: CI on branch-4.1 draws enable_common_expr_pushdown at
random for each session. With it off, MATCH is not evaluated with the
inverted index in the scan, so no BM25 score is collected and score()
returns 0. test_cte_inline_virtual_column got score 0.0 for its
TopN. Like the score suites of the branch, the suite sets
enable_common_expr_pushdown = true.

### Release note

None

### Check List (For Author)

- Test: Regression test. With use_fuzzy_session_variable = true and
the pull request number of CI, the suite failed in sessions that
drew enable_common_expr_pushdown = false; with the setting pinned,
four runs passed.
- Behavior changed: No
- Does this need documentation: No

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…#69399 (#69563)

### What problem does this PR solve?

Related PR: #69399

Problem Summary: Backport #69399 to `branch-4.1`.

A CTE fails to plan with "A expression contains slot not from children"
when the optimizer inlines it after one of its scans got a virtual
column: a CTE that orders by `score()` or by an ANN distance with a
LIMIT, or that has MATCH in its select list and is inlined after
rewrite. `LogicalPlanDeepCopier` gave each virtual column two ids,
copied them in list order, kept the old slot in the output of the copied
scan and left the score and ANN order keys on the old slots. The copier
now maps every virtual column to its new id before copying their
expressions and remaps the order keys, and
`LogicalOlapScan.withVirtualColumns` replaces the old virtual slots in
the output.

#### Branch adaptations

The branch has no table streams, so the change to
`LogicalOlapTableStreamScan` is dropped. `withVirtualColumns` keeps the
constructor call of the branch, and `LogicalPlanDeepCopierTest` and
`CTEInlineTest` keep the tests of the branch and add the tests of
#69399. `test_cte_inline_virtual_column` sets
`enable_common_expr_pushdown = true`, as the score suites of the branch
do: CI on branch-4.1 draws it at random for each session, and without it
MATCH is not evaluated with the index in the scan and `score()` is 0.

### Release note

Fix "A expression contains slot not from children" for a CTE that orders
by `score()` or by an ANN distance with a LIMIT, or that has MATCH in
its select list and is inlined after rewrite.

### Check List (For Author)

- Test
    - [x] Regression test
    - [x] Unit Test
    - [ ] Manual test
- Behavior changed:
    - [x] No.
- Does this need documentation?
    - [x] No.

### Validation

Validated together with the other two backports (#69399, #69419 and
#69292 on `branch-4.1` at 3f911d0), in a local ASAN build:

- PASS: FE unit tests `LogicalPlanDeepCopierTest`, `CTEInlineTest`,
`InferPredicateByReplaceTest`, `InferPredicatesTest`,
`UnequalPredicateInferTest`, `BindScoreToOlapScanTest`,
`SearchExpressionTest`, `TopNRuntimeFilterTest` and
`MaterializedViewUtilsTest` (228 tests), and FE Checkstyle.
- PASS: `./build.sh --be` and `./build.sh --fe`.
- PASS: BE unit tests `SegmentIteratorScoreCommonExprTest`,
`SegmentIteratorApplyIndexExprTest` and `VirtualSlotRefTest` (31 tests);
clang-format 16 on the changed BE files.
- PASS: the 16 regression suites of the branch that use `score()`,
including `test_cte_inline_virtual_column`, `infer_match_predicate`,
`test_score_filter_usage` and `test_score_filter_matrix`. The framework
regenerated the `.out` of `test_score_filter_matrix` on this branch: it
drops the 46 SNII cases and keeps the 94 V2 and V3 cases of master
unchanged. The other `.out` files are unchanged.
- PASS: with the fuzzy session variables of CI
(`use_fuzzy_session_variable = true` and its pull request number), the
score suites failed in sessions that drew `enable_common_expr_pushdown =
false`; with the setting pinned, four runs of `test_score_filter_usage`,
`test_score_filter_matrix` and `test_cte_inline_virtual_column`, and
four of `infer_match_predicate`, passed.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <[email protected]>

…cross column equalities #69419 (#69564)

### What problem does this PR solve?

Related PR: #69419

Problem Summary: Backport #69419 to `branch-4.1`.

Predicate inference copied a predicate on one column to every column
that is equal to it, also when the predicate contained MATCH,
multi_match or SEARCH. Their result depends on the inverted index of the
column, not only on its value: with `c1 = c2` and different parsers on
the two columns, the copy removed matching rows, and with the same index
it doubled `score()`, so a minimum score let low-scored rows through.
`InferPredicateByReplace.infer` now skips every input that contains
`Match`, `MultiMatch`, `Search` or `SearchExpression`.

#### Branch adaptations

The branch does not have the `NoneMovableFunction` check that master has
next to the new check, so only the new check is added. The test imports
`SearchDslParser` from its package on the branch.
`infer_match_predicate` sets `enable_common_expr_pushdown = true`, as
the score suites of the branch do: CI on branch-4.1 draws it at random
for each session, and without it MATCH is not evaluated with the index
in the scan and `score()` is 0.

### Release note

Fix wrong results and scores when predicate inference copied a MATCH,
multi_match or SEARCH predicate to an equal column.

### Check List (For Author)

- Test
    - [x] Regression test
    - [x] Unit Test
    - [ ] Manual test
- Behavior changed:
- [x] Yes. Predicate inference no longer copies a predicate that
contains MATCH, multi_match or SEARCH to an equal column.
- Does this need documentation?
    - [x] No.

### Validation

Validated together with the other two backports (#69399, #69419 and
#69292 on `branch-4.1` at 3f911d0), in a local ASAN build:

- PASS: FE unit tests `LogicalPlanDeepCopierTest`, `CTEInlineTest`,
`InferPredicateByReplaceTest`, `InferPredicatesTest`,
`UnequalPredicateInferTest`, `BindScoreToOlapScanTest`,
`SearchExpressionTest`, `TopNRuntimeFilterTest` and
`MaterializedViewUtilsTest` (228 tests), and FE Checkstyle.
- PASS: `./build.sh --be` and `./build.sh --fe`.
- PASS: BE unit tests `SegmentIteratorScoreCommonExprTest`,
`SegmentIteratorApplyIndexExprTest` and `VirtualSlotRefTest` (31 tests);
clang-format 16 on the changed BE files.
- PASS: the 16 regression suites of the branch that use `score()`,
including `test_cte_inline_virtual_column`, `infer_match_predicate`,
`test_score_filter_usage` and `test_score_filter_matrix`. The framework
regenerated the `.out` of `test_score_filter_matrix` on this branch: it
drops the 46 SNII cases and keeps the 94 V2 and V3 cases of master
unchanged. The other `.out` files are unchanged.
- PASS: with the fuzzy session variables of CI
(`use_fuzzy_session_variable = true` and its pull request number), the
score suites failed in sessions that drew `enable_common_expr_pushdown =
false`; with the setting pinned, four runs of `test_score_filter_usage`,
`test_score_filter_matrix` and `test_cte_inline_virtual_column`, and
four of `infer_match_predicate`, passed.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <[email protected]>

…69292 (#69565)

### What problem does this PR solve?

Related PR: #69292

Problem Summary: Backport #69292 to `branch-4.1`. It contains the commit
of #69563, the backport of #69399, which it needs: binding runs before
CTE inlining, which copies scans with virtual columns. Merge #69563
first.

`score()` only worked as `ORDER BY score() LIMIT n` directly above the
scan whose MATCH defines it. A minimum score filter without that TopN
evaluated the unbound `score()` placeholder as zero and silently dropped
every row:

```sql
SELECT id FROM documents WHERE content MATCH 'apple' AND score() > 0.00001;  -- returned nothing
```

`BindScoreToOlapScan`, which replaces `CheckScoreUsage`, binds `score()`
to the scan of its SELECT at the start of rewrite and rejects the uses
it cannot bind. The minimum score stays a predicate of the scan, and
`PushDownScoreTopNIntoOlapScan` still pushes a TopN on the score
together with the minimum. In the BE, an expression on the score reads
the score column instead of evaluating `Score()`, and MATCH projections
do not add to the score. See #69292 for the supported and rejected uses.

#### Branch adaptations

- The `SegmentIterator` of the branch collects the columns of
pushed-down expressions in `_extract_common_expr_columns` instead of
per-column states, so the score column is marked there, and the new BE
test checks `_common_expr_columns` and `_is_common_expr_column`. The
branch reads the columns collected there before it evaluates the
expressions, also virtual ones, and a virtual slot uses a column that is
already read.
- The branch evaluates MATCH projections with `evaluate_inverted_index`
directly, and that loop runs without the score collector.
- `PushDownScoreTopNIntoOlapScan` keeps the overflow check of the branch
for `limit + offset`, which fails like master does.
- `SearchDslParser` and `CollectionSimilarity` are included from their
packages on the branch.
- The branch has no SNII storage format, so `BindScoreToOlapScanTest`
and `test_score_filter_matrix` cover V2 and V3, and the `.out` of
`test_score_filter_matrix` is regenerated without the SNII cases.
- The branch does not have #68672, which keeps predicates on virtual
columns out of the condition cache. The minimum score is now a predicate
of the scan, and a score depends on every rowset, so a cached result
goes stale when a rowset is added: without the change,
`test_score_filter_matrix` lost the rows of the first rowset.
`VirtualSlotRef::get_digest` returns 0 as on master, the part of #68672
that this needs, with the `VirtualSlotRef` tests of #68672 that the
branch can run.
- `test_score_filter_usage`, `test_score_filter_matrix` and
`test_cte_inline_virtual_column` set `enable_common_expr_pushdown =
true`, as the score suites of the branch do: CI on branch-4.1 draws it
at random for each session, and without it MATCH is not evaluated with
the index in the scan and `score()` is 0.

### Release note

`score()` works in the select list, window functions and ORDER BY of a
SELECT on one table whose WHERE clause has MATCH or SEARCH, with an
optional minimum score `score() > x` or `score() >= x`, without `ORDER
BY score() LIMIT`. A scored SELECT in a subquery, view, CTE or set
operation still needs `ORDER BY score() LIMIT`. Other uses of `score()`
are rejected instead of evaluating it as 0.

### Check List (For Author)

- Test
    - [x] Regression test
    - [x] Unit Test
    - [ ] Manual test
- Behavior changed:
- [x] Yes. A minimum score works without `ORDER BY score() LIMIT`, and
unsupported uses of `score()` fail planning instead of evaluating it as
0. A minimum score without a TopN needs the BE change, so BEs must be
upgraded before FEs.
- Does this need documentation?
- [x] Yes. The `score()` documentation should describe where `score()`
can be used.

### Validation

Validated together with the other two backports (#69399, #69419 and
#69292 on `branch-4.1` at 3f911d0), in a local ASAN build:

- PASS: FE unit tests `LogicalPlanDeepCopierTest`, `CTEInlineTest`,
`InferPredicateByReplaceTest`, `InferPredicatesTest`,
`UnequalPredicateInferTest`, `BindScoreToOlapScanTest`,
`SearchExpressionTest`, `TopNRuntimeFilterTest` and
`MaterializedViewUtilsTest` (228 tests), and FE Checkstyle.
- PASS: `./build.sh --be` and `./build.sh --fe`.
- PASS: BE unit tests `SegmentIteratorScoreCommonExprTest`,
`SegmentIteratorApplyIndexExprTest` and `VirtualSlotRefTest` (31 tests);
clang-format 16 on the changed BE files.
- PASS: the 16 regression suites of the branch that use `score()`,
including `test_cte_inline_virtual_column`, `infer_match_predicate`,
`test_score_filter_usage` and `test_score_filter_matrix`. The framework
regenerated the `.out` of `test_score_filter_matrix` on this branch: it
drops the 46 SNII cases and keeps the 94 V2 and V3 cases of master
unchanged. The other `.out` files are unchanged.
- PASS: with the fuzzy session variables of CI
(`use_fuzzy_session_variable = true` and its pull request number), the
score suites failed in sessions that drew `enable_common_expr_pushdown =
false`; with the setting pinned, four runs of `test_score_filter_usage`,
`test_score_filter_matrix` and `test_cte_inline_virtual_column`, and
four of `infer_match_predicate`, passed.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <[email protected]>