Blazing supports AWS s3 and MinIO by overriding the endpoint. Thus, with non virtual host style bucket access it seems blazing context can not load a table from s3.
Possible solutions
Support s3 client overriding (e.g. using s3fs as a filesystem params like in pandas)
Support extra parameters to specify path-style access or virtual host style access
Allow building blazing tables using a file descriptor's like object (emancipating from s3 adherence)
----For BlazingSQL Developers----
The feature could be implemented directly in table creation methods as a parameter or set of parameters
We will be embarking on a filesystem plugin system refactoring project in the near future. We will keep in mind this issue when we do so. Thank you for bringing this issue to our attention
Blazing supports AWS s3 and MinIO by overriding the endpoint. Thus, with non virtual host style bucket access it seems blazing context can not load a table from s3.
Possible solutions
----For BlazingSQL Developers---- The feature could be implemented directly in table creation methods as a parameter or set of parameters