mrhhsg opened a new pull request, #69963: URL: https://github.com/apache/doris/pull/69963
### What problem does this PR solve? Issue Number: None SEARCH expressions need the inverted-index path, but disabling common-expression pushdown can leave them in ordinary scanner filtering, where they cannot execute. Remote DATE runtime filters can also lose their DATE type when deserialized as DATETIME. Separately, a Variant schema-change regression used a value whose text representation depended on whether insertion happened before or after a DOUBLE-to-TEXT change. ### What is changed? - Keep SEARCH-containing scan predicates on the inverted-index path when common-expression pushdown is disabled, subject to the existing no-merge and slot constraints. - Disable scan condition-cache reuse for SEARCH predicates because the cache digest does not include the SEARCH DSL. - Decode remote DATE IN and MIN/MAX filter values as DATE, while preserving the existing DATETIME behavior. - Use a stable Variant schema-change input and verify that successful writes remain visible after the schema change, including a separate post-DDL write. ### Test Plan - `BUILD_TYPE=ASAN ./build.sh --be --fe` — passed. - Targeted BE unit tests for DATE IN/MIN/MAX runtime filters and SEARCH expressions — 51 passed. - Isolated local regression suites `inverted_index_p0/test_search_score_topn_predicates`, `datatype_p0/datev1/test_datev1_common`, and Variant schema-change v1/v2 — each passed; updated expected outputs were generated and rerun. - `build-support/check-format.sh`, `clang-format`, and `git diff --check` — passed. - Full regression, multi-BE runtime-filter distribution, mixed-version testing, and benchmarks were not run locally. ### Release note SEARCH queries retain inverted-index execution when common-expression pushdown is disabled, and remote DATE runtime filters retain their DATE type. -- 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]
