> 3. Given our limited API sets, what would you recommend?
The filesystem interface is already rather minimal. We generally
don't put a function in there if we aren't using it somewhere. That
being said, you can often get away with a mock implementation. From a
quick rundown:
HI Jae,
Mainly providing an answer on your first question:
On Thu, 10 Feb 2022 at 05:06, Jae Lee wrote:
> Hi Team,
>
> I would like to implement a custom subclass of
> pyarrow.filesystem.FileSystem (or perhaps pyarrow.fs.FileSystem) and was
> hoping to leverage the full potential of what
Hi Team,
I would like to implement a custom subclass of
pyarrow.filesystem.FileSystem (or perhaps pyarrow.fs.FileSystem) and was
hoping to leverage the full potential of what pyarrow provides with parquet
files - partitioning, filter, etc. The underneath storage is cloud-based
and not S3
