Rich-T-kid commented on issue #3199:
URL: https://github.com/apache/arrow-rs/issues/3199#issuecomment-5444599420
> Probably arrow-schema is best
make sense to me.
>Since what "semantically compatible" means may be pretty specific to each
use case, I am not sure how much value moving the code to arrow-rs would bring
I was thinking of introducing an enum/struct that would serve as a gauge for
how in-depth the comparison would be:
```
struct EquivalenceGauge {
check_nullability: bool,
check_field_name: bool,
check_metadata: bool,
}
```
`fn compare_datatype(dt_1: &DataType, dt_2: &DataType, eq: EquivalenceGauge)
-> bool`
decided to go with a struct since it allows us to update this in the future
without making it a breaking api change
--
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]
