> The discussion in ARROW-6206 contains some mildly offensive language
> directly at the Arrow community, like "arrow is a team that picked up
> netty derived off-heap tools naively". Excuse me?
I'm trying my best to ignore language that isn't really productive to
solving technical problems :) If
hi Micah,
I agree that documenting the maturity of components is a good idea.
The discussion in ARROW-6206 contains some mildly offensive language
directly at the Arrow community, like "arrow is a team that picked up
netty derived off-heap tools naively". Excuse me? Documentation aside,
I think s
A recent issue with the JDBC adapter [1] made me realize we aren't doing
enough to communicate to consumers the maturity of various modules within
arrow. From the issue, it also seems like it is surprising that everything
is based off of off-heap data access.
To help with this I added a descripti
