Willem-J-an commented on PR #416:
URL: https://github.com/apache/arrow-go/pull/416#issuecomment-3045997065

   
![Screenshot_2025-07-07-19-14-51-05_fd7367fd0afc7e864f00091a00b3d0b0](https://github.com/user-attachments/assets/3cfa6a9c-aef5-480e-9f02-2121883c66d9)
   
   My example was fixed binary, notice it shows up twice in above screenshot. I 
observed the fixed binary to return an array, as is described in the screenshot 
as well.
   
   The case didn't apply because when I use arrow reader it converts to array, 
not to map and not to slice. I don't know if there's a scenario where it would 
actually be used, that's my question! I suppose if hamba doesn't decode into 
slice or map for fixed bytes, is there any other decoder that users can use 
that do hit these code paths? If not than maybe these are only applicable to 
hamba v1 or so, and not needed anymore.
   
   If you're unsure we can also just leave it. The most important part for me 
is to have the working cases added, rather than the not working cases removed.
   
   And fixed binary was an example, the same applies to timestamps and the 
other types I fixed. 


-- 
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: github-unsubscr...@arrow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to