You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: Attach Diagnostic to more than one column errors in scalar_subquery and in_subquery (#15143)
* feat: diagnostic to more than one column error
* test: improve test case
* feat: multiple "in" queries diagnostic
* refactor: reuse code in subquery.rs
* chore: clearer note message
* fix: use plain Spans
* fix: better error messages
* fix: remove the specific subquery type
* fix: use iter_union to create full_span
* fix: CI fail problems
* Update expected error message
---------
Co-authored-by: Andrew Lamb <andrew@nerdnetworks.org>
Copy file name to clipboardExpand all lines: datafusion/optimizer/src/scalar_subquery_to_join.rs
+2-6Lines changed: 2 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -731,9 +731,7 @@ mod tests {
731
731
.project(vec![col("customer.c_custkey")])?
732
732
.build()?;
733
733
734
-
let expected = "Invalid (non-executable) plan after Analyzer\
735
-
\ncaused by\
736
-
\nError during planning: Scalar subquery should only return one column";
734
+
let expected = "Error during planning: Scalar subquery should only return one column, but found 4: orders.o_orderkey, orders.o_custkey, orders.o_orderstatus, orders.o_totalprice";
0 commit comments