maartenbreddels commented on pull request #7449:

   > I'd like to treat in-kernel type promotions as an anti-pattern in general.
   There are upsides and downsides to it. The downside is that users of the 
Arrow library are exposed to the implementation details of how each kernel can 
grow the resulting array. I see this being quite a burden in vaex, to keep 
track of which kernel does what, and when to promote.
   Vaex does something similar, slicing the array's in smaller chunks, but 
still, it would need to check the sizes, no matter how small the slices are.
   Maybe it's best to keep this PR simple first (so give an error?), and 
discuss the behavior of string growth on the mailing list?

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

Reply via email to