github-actions[bot] commented on code in PR #66788:
URL: https://github.com/apache/doris/pull/66788#discussion_r3790955547
##########
fe/fe-core/src/main/java/org/apache/doris/qe/SessionVariable.java:
##########
@@ -3513,6 +3515,10 @@ public void
checkAnnIndexCandidateRowsPercentThreshold(String value) {
description = "Enable extended regular expressions, support
look-around zero-width assertions")
public boolean enableExtendedRegex = false;
+ @VarAttrDef.VarAttr(name = ENABLE_HYPERSCAN_FALLBACK, needForward = true,
affectQueryResultInExecution = true,
Review Comment:
[P2] Preserve strict mode in asynchronous MTMV refreshes
`CREATE MATERIALIZED VIEW` persists only
`getAffectQueryResultInPlanVariables()`, and
`MTMVPlanUtil.createBasicMvContext()` restores only that plan-affecting map.
Because this field is marked only `affectQueryResultInExecution`, a creator's
`enable_hyperscan_fallback=false` is already lost before the first background
refresh: a definition with `WHERE value_col REGEXP 'a{51}'` runs under the
fresh context's default `true` and falls back instead of returning the
requested strict error. Persist and restore this policy in MTMV task contexts
and cover both initial refresh and replay. This is distinct from the existing
synchronous-ALTER replay thread because MTMV drops the value through its
separate session map before the first refresh.
--
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]
