Xuanwo
I'm thinking about this for a while. One possible idea is we can store an `LazyCell` in `Reader` which can only be filled once after users start a real read....
Thank you for bringing this up. > That is, if there's no good reason for restricting the charset of that string - is there, in this case??? The HTTP specifications...
> I see a little bit of value in forcing all requests to use TLS even if some path may specify the plain text variant. Especially when users use SAS...
Thank you for this report, I'll take a look.
Hi @mkleinbort-wl, I've done some research on this issue and have a gussing it might be related to a recent change in Polars. Could you share the version of Polars...
> I'm on: > > polars = `1.32.3` lancedb = `0.25.0` pylance (lance) = `0.35.0` Thank you for this, I will come a fix for this.
I'm thinking about adding `reader` and `writer` so users can control the underlying data operations. I'm not sure if it's much better to have an opendal-cpp instead.
> We could have an opendal cpp binding, but cbindgen generates reletively the same library and header files. Hence the implementation is roughly the same. I'm thinking about cxx instead....
> * Future APIs (append(), etc.) Please note that `append` has been removed: it's now `op.write_with("path", bs).append(true).await`
Hi @youngsofun, could you check this issue? It seems we didn't correctly read the orc file.