Open tanho63 opened 3 months ago
Yes, we could definitely do one or both of those. The challenge for the HTTP is to keep the package lean, but reading from a raw vector is pretty straightforward. write_parquet()
already supports writing to a raw vector.
Btw. we could also support reading from an R connection, then you could do
read_parquet(url("https://...."))
either of these would be great!
Reading from a connection would be great as that's how we read rds files from url!
To clarify, for a Parquet file, reading from a connection means that we would need to read the whole file first, save it to a temporary file, and then read it from there.
Which you can also do relatively easily as a workaround.
Dev version can read from a connection now.
Hi! Excited by the looks of this package. A frequent use case I have is reading a parquet from a URL, e.g.
Is this something that would be in-scope for nanoparquet?