You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Handle only regular columns (= numpy arrays) for now.
"""
_VaexBuffer.__init__() is private API, but affects interchange with different libraries as this is called when using the public API of Column.get_buffers()
So obviously it'd be nice (if not practically essential?) if vaex supported interchanging Arrow-backend columns too. I just thought to raise this issue as a tracker, as I didn't quite see relevant conversation in #1509. cc @maartenbreddels
The text was updated successfully, but these errors were encountered:
Even if the buffer is stored as numpy array, it can still mean the underlying data is an arrow array.
I think it should be possible to do arrow->protocol->arrow without a memory copy. At least that's how we designed the spec AFAIKR. It could be that the implementation is missing some parts still.
Initialising an interchange protocol buffer (
_VaexBuffer
) only works for vaex columns with NumPy backendsvaex/packages/vaex-core/vaex/dataframe_protocol.py
Lines 241 to 244 in 35c250d
_VaexBuffer.__init__()
is private API, but affects interchange with different libraries as this is called when using the public API ofColumn.get_buffers()
So obviously it'd be nice (if not practically essential?) if vaex supported interchanging Arrow-backend columns too. I just thought to raise this issue as a tracker, as I didn't quite see relevant conversation in #1509. cc @maartenbreddels
The text was updated successfully, but these errors were encountered: