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
Previously, these errors would occurr during optimization. Now that we
allow unbound placeholders through the optimizer they fail when creating
the physical plan instead.
// so the filter data type is not know, i.e. a = $0.
2011
-
// Therefore, the optimization fails.
2012
-
let optimized_plan = ctx.state().optimize(logical_plan);
2013
-
assert!(optimized_plan.is_err());
2014
-
assert!(optimized_plan
2015
-
.unwrap_err()
2016
-
.to_string()
2017
-
.contains("Placeholder type for '$0' could not be resolved. Make sure that the placeholder is bound to a concrete type, e.g. by providing parameter values."));
2018
-
2019
-
// Prodiving a parameter value should resolve the error
2010
+
// Executing LogicalPlans with placeholders that don't have bound values
2011
+
// should fail.
2012
+
let results = df.collect().await;
2013
+
let err_mesg = results.unwrap_err().strip_backtrace();
2014
+
assert_eq!(
2015
+
err_mesg,
2016
+
"Execution error: Placeholder '$0' was not provided a value for execution."
2017
+
);
2018
+
2019
+
// Providing a parameter value should resolve the error
.contains("Placeholder type for '$1' could not be resolved. Make sure that the placeholder is bound to a concrete type, e.g. by providing parameter values."));
2076
+
// Executing LogicalPlans with placeholders that don't have bound values
.contains("Placeholder type for '$1' could not be resolved. Make sure that the placeholder is bound to a concrete type, e.g. by providing parameter values."));
2146
+
// Executing LogicalPlans with placeholders that don't have bound values
0 commit comments