4paradigm / 4paradigm/OpenMLDB
WARN log "not fully resolved" for SQL `select 0 in ("0","2")`
- Lenguaje dominante
- C++
- Estrellas
- 1.7k
- Forks
- 331
- Merge medio
- 12 d 12 h
- PR fusionados (30 d)
- 1
Descripción
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`?
Guía de contribución
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- cpp, sql
- Área
- databases, machine-learning
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 45/100