aihuaxu commented on PR #455: URL: https://github.com/apache/arrow-go/pull/455#issuecomment-3140553874
> > My preference would be to relax the spec for this issue. It doesn't seem like there's much benefit to enforcing it on the read side, and it's easy to imagine a writer failing to enforce it in some cases where it usually adds a `typed_value` to the schema, but not always. > > +1 > > IIRC, these wordings are by purpose to not complicate the reader side implementation w.r.t. reading values and consuming column stats directly from `typed_value`. <img width="1058" height="204" alt="image" src="https://github.com/user-attachments/assets/4baf1afb-6856-473d-ba1d-673d4edc9d1d"; /> I think we can update the wording "When typed_value is omitted, value must be required." => "When typed_value is omitted, value must be present.". both typed_value and value fields should always be optional but we are saying it's required and that is causing the confusion. -- 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...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
