4paradigm / 4paradigm/OpenMLDB
WARN log "not fully resolved" for SQL `select 0 in ("0","2")`
- Langage dominant
- C++
- Étoiles
- 1.7k
- Forks
- 331
- Merge moyen
- 12 j 12 h
- PR mergées (30 j)
- 1
Description
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`?
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- cpp, sql
- Domaine
- databases, machine-learning
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 45/100