Skip to content

Conversation

@MisterRaindrop
Copy link
Contributor

@MisterRaindrop MisterRaindrop commented Jan 29, 2026

I have implemented Arrow FileSystem to access S3, but I'm still not sure if it meets the requirements.

There are still task or question to complete for the current PR, and it is not ready for merging yet.

Question:
Currently, the object storage options include Azure, AWS, and GCS. I have chosen AWS as the implementation for now is ok?

Task:
I need to deploy MinIO to facilitate testing access to S3, but I'm not sure where it would be best to set it up?

@wgtmac
Copy link
Member

wgtmac commented Jan 29, 2026

Thanks for adding this!

I have chosen AWS as the implementation for now is ok?

Yes, I believe this is worth doing. I supposed to reuse ArrowFileSystemFileIO by passing an arrow::FileSystem of S3 which is supported by Arrow if built with ARROW_S3=ON. But I haven't explored it yet.

I need to deploy MinIO to facilitate testing access to S3

There is a related discussion with regard to minio's recent license change: https://lists.apache.org/thread/vnw9jonmfcsz6bwojhfch1nmywyl50h3. I'm not sure if there is any good alternative to test it.

@MisterRaindrop
Copy link
Contributor Author

I recommend using MinIO. It is relatively stable and suitable for the current project development phase. Once the community reaches a consensus, the cost of replacing MinIO will not be high.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants