ZENOTME opened a new issue, #11468:
URL: https://github.com/apache/arrow-rs/issues/11468

   ### Is your feature request related to a problem or challenge?
   
   `cast_with_options` returns `ArrowError::CastError(String)` for both:
   - A supported conversion that fails because an input value cannot be 
converted.
   - A conversion between types that is not supported.
   
   These failures have different meanings, but callers cannot distinguish them 
by matching the error variant. For downstream query engines, this distinction 
is useful for deciding which error to expose to users—for example, an invalid 
data value versus an unsupported operation. 
   
   
   
   ### Describe the solution you'd like
   
   1. Return ArrowError::NotYetImplemented consistently for unsupported type 
conversions, reserving CastError for failures when converting input values.
   2. Add a structured kind to CastError, allowing callers to distinguish 
reasons such as UnsupportedConversion and InvalidValue while retaining the 
diagnostic message.
   Either approach would let callers distinguish these cases without parsing 
error strings.
   
   ### Describe alternatives you've considered
   
   _No response_
   
   ### Additional context
   
   _No response_


-- 
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]

Reply via email to