adamreeve commented on issue #267:
URL: https://github.com/apache/arrow-dotnet/issues/267#issuecomment-7026754642

   > would not conform to the Arrow specification
   
   I think this is a bit strong. The Arrow specification just says 
"Implementations are recommended to allocate memory on aligned addresses". So 
my interpretation is that non-aligned buffers are still conformant with the 
spec. And consumers should expect to have to handle data that may not be 
64-byte aligned.
   
   Alignment in IPC files is required, but this is independent of the memory 
allocator used, so that's not a problem.
   
   The C Data Interface spec also says that alignment is a recommendation, but 
that "Consumers MAY decide not to support unaligned memory". So for 
full-compatibility with any consumers, alignment is required in practice. It 
looks like unaligned buffers for types wider than 8 bytes (eg. `Decimal128`) 
could cause problems with some implementations. This might require a copy into 
aligned memory if exporting from arrow-dotnet and consuming from an 
implementation that requires type-width alignment (eg. arrow-rs does this).


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to