tustvold commented on PR #6157:
URL: https://github.com/apache/arrow-rs/pull/6157#issuecomment-2309724961

   So long as we don't break existing workloads, I don't see an issue. However, 
I will observe that the code commonality between a suffix and range based 
MetadataLoader will likely be relatively small... Rather than adding code to 
support what is a fairly niche use-case, it might be worth this living in a 
repository dedicated to WASM support? Given the first-party S3 implementation 
doesn't support WASM32, let alone CORS-filtered responses that are missing 
expected headers, I suspect you must be rolling your own anyway?


-- 
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]

Reply via email to