4paradigm / 4paradigm/OpenMLDB

WARN log "not fully resolved" for SQL `select 0 in ("0","2")`

未关闭
#2,845 1 条评论 0 个 reaction 已指派 1 人 已被 @aceforeverd 认领 在 GitHub 查看
execute-engine minor
主要语言
C++
星标
1.7k
派生
331
平均合并
12 天 12 小时
30 天内合并 PR
1

描述

test sql `select 0 in ("0","2");`
It'll print `expr_ir_builder.cc:98] (0,2) not fully resolved`.
But we skip InferAttr when node is expr list, in
https://github.com/4paradigm/OpenMLDB/blob/ea0a7bcc13f37110b9072972c59dec483935c93a/hybridse/src/passes/resolve_fn_and_attrs.cc#L246

So the WARN log should be print if `output type ==nullptr && node expr type != kExprList`?

贡献指南

打开贡献指南

调研方向

The issue points to hybridse/src/passes/resolve_fn_and_attrs.cc line 246, where InferAttr is skipped for expression lists. Examine the logic around expr_ir_builder.cc:98 to understand when the 'not fully resolved' warning is printed. Check the condition for output type and node expression type to see if the warning is appropriate. Run the test SQL `select 0 in ("0","2");` to reproduce the warning and verify the fix.

由索引模型根据 Issue 内容生成。

评估

技术栈
cpp, sql
领域
databases, machine-learning
Issue 类型
缺陷
难度
3/5
预计耗时
1-2 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
45/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。