Kenta Murata writes:
> Hi Jed,
>
> I'd like to describe the current status of the implementation of SparseTensor.
> I hope the following explanation will help you.
>
> First of all, I designed the current SparseTensor format as the first
> interim implementation.
> At this time I used scipy.spars
Hi Jed,
I'd like to describe the current status of the implementation of SparseTensor.
I hope the following explanation will help you.
First of all, I designed the current SparseTensor format as the first
interim implementation.
At this time I used scipy.sparse as a reference.
The reason why I s
Thanks. I'm new to the Arrow community so was hoping to get feedback if
any of these are controversial or subject to constraints that I'm likely
not familiar with. Point 2 is likely simplest and I can start with
that.
Point 3 isn't coherent as a PR concept, but is a potential audience
whose rela
hi Jed,
Would you like to submit a pull request to propose the changes or
additions you are escribing?
Thanks
Wes
On Sat, Mar 9, 2019 at 11:32 PM Jed Brown wrote:
>
> Wes asked me to bring this discussion here. I'm a developer of PETSc
> and, with Arrow is getting into the sparse representatio
Wes asked me to bring this discussion here. I'm a developer of PETSc
and, with Arrow is getting into the sparse representation space, would
like for it to interoperate as well as possible.
1. Please guarantee support for 64-bit offsets and indices. The current
spec uses "long", which is 32-bit o
