alamb commented on issue #6129: URL: https://github.com/apache/arrow-rs/issues/6129#issuecomment-2287197543
> EDITED: I just saw https://github.com/apache/arrow-rs/pull/6197 which feels relevant to the 1st one. I agree. We are also looking for help with the reading portion -- see comments on https://github.com/apache/arrow-rs/issues/6002 cc @adriangb > [finding the index given the column dot-string path](https://github.com/apache/arrow/blob/main/cpp/src/parquet/schema.h#L429-L434), There is something similar here https://docs.rs/parquet/latest/parquet/arrow/fn.parquet_column.html but adding a real API that handles the field resolution logic for nested fields would be very nice. Perhaps you can file a ticket requesting this feature (I have found clearly worded tickets are very often picked up by people in this community) > For the last one, there's a [Type struct](https://github.com/apache/arrow-rs/blob/master/parquet/src/schema/types.rs#L40-L59) in the codes which seems similar to the C++ [Node](https://github.com/apache/arrow/blob/main/cpp/src/parquet/schema.h#L96-L98). I'm currently am not sure how complex or whether it worths the effort to support a field-tree with parent info in the current codes? But a simple way might be maintaining a Vec<Option<TypePtr>> that marks the parent of each Type, while adding an index to each Type? I am not familiar with the usecase for finding the parent of a field so I don't have much to add to this -- 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]
