Silemo opened a new issue, #5677: URL: https://github.com/apache/arrow-rs/issues/5677
**Which part is this question about** <!-- Is it code base, library api, documentation or some other part? --> Hi there! Young dev here. I recently opened an issue about having HDFS support, and after your suggestions I am now working on a refactor of [datafusion-contrib/datafusion-objectstore-hdfs](https://github.com/datafusion-contrib/datafusion-objectstore-hdfs). While working there I noticed a problem that can easily be solved with a change in some modules visibility. **Describe your question** <!-- A clear and concise description of what the question is. --> Would it be possible to refactor the current repo so to be able to expose object_store::util::maybe_spawn_blocking, object_store::util::PutPayLoad, object_store::upload::MultipartUpload? **Additional context** <!-- Add any other context about the problem here. --> This is necessary as an external implementation of the ObjectStore, needs these objects and method to implement the interface. Leaving the visibility like this would mean that I would make a copy of the object_store::util::maybe_spawn_blocking method, as [currently is in the datafusion-contrib/datafusion-objectstore-hdfs](https://github.com/datafusion-contrib/datafusion-objectstore-hdfs/blob/master/hdfs/src/object_store/hdfs.rs#L578). Looking in-depth to various of the object_store implementation that you have in the repo, you often import these methods using crate:: , but this is not possible for external repositories. I think that this change would enable external implementation of the ObjectStore interface to be complete and use the code already present in this repository. -- 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]
