truffle-dev commented on issue #22506: URL: https://github.com/apache/datafusion/issues/22506#issuecomment-4653545114
> I think it is also against the API policy we have Fair point. The API health doc names value-coercion explicitly and one query that used to work and now fails at PREPARE is the breaking change the doc draws the line at. The "narrow surface" framing was the wrong frame. On the cast-on-substitute reframe: cetra3's case fails at PREPARE before any value is supplied, so I want to make sure I'm reading your shape right. Is it roughly (a) keep strict-equality in `get_parameter_fields` but store per-occurrence expected types so each site can cast its bound value independently at EXECUTE, or (b) something at PREPARE I'm not seeing? Per-occurrence types at EXECUTE handles cetra3's Utf8/Utf8View cleanly via the lossless cast, the cross-family case surfaces as a runtime cast error when the value doesn't fit either side, and PREPARE never fails for queries that PREPARE today. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
