jayzhan211 commented on issue #12622: URL: https://github.com/apache/datafusion/issues/12622#issuecomment-2668605924
> Did you mean physical planner? Physical plan is statically typed, and uses DataType, If we go from LP to PP, we need to use types correctly (just as we need to use correct types when going from SQL text to LP For example, the existing type coercion coerce string to exact DataType::Utf8, so if we have `DataType::Utf8` and `DataType::Utf8View`, we end up both `DataType::Utf8View`. If the type coercion in LP only take care about NativeType::String and we end up with `DataType::Utf8` and `DataType::Utf8View`. We consider these resolved types in LP. Then, we continue type coercion in PP where we can coerce `DataType::Utf8` to `DataType::Utf8View` for performance reason or whatever. BUT, we don't do coercion in LP with Int and String coercion which has different NativeType, so even i32 and i64 is not allowed. Does this makes sense to you? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
