0x26res commented on PR #35113: URL: https://github.com/apache/arrow/pull/35113#issuecomment-1510902015
Are we then saying that: - This field is pure meta data and it's left to the user to provide sorted keys? - it won't be enforced by arrow? For context, I'm not really using that field. I just need to be able to access it in order to create slightly modified copies of schemas. For example if I want to change the type of nested fields (int32 -> int64). Then I need to make copy of `pa.map_ ` types, preserving the keys_sorted metadata. | So maybe the question is do we want to add a check for it in PyArrow Array and Scalar? Maybe we should create a follow up issue to do this. It would involve making some change that may break some stuff at runtime (if someone was previously providing unsorted data with `keys_sorted=True`). As far as this MR is concerned, I think we should just improve the doc for that field (and probably update the doc in the C++ MapType class). -- 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]
