[GitHub] [arrow] wesm commented on pull request #6725: ARROW-8226: [Go] Implement 64 bit offsets binary builder

2020-06-26 Thread GitBox


wesm commented on pull request #6725:
URL: https://github.com/apache/arrow/pull/6725#issuecomment-650356376


   Well, that is definitely a bummer. I hope to see some growth in the Go 
developer community here in the future. I'll close this PR for now then



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:
us...@infra.apache.org




[GitHub] [arrow] wesm commented on pull request #6725: ARROW-8226: [Go] Implement 64 bit offsets binary builder

2020-06-24 Thread GitBox


wesm commented on pull request #6725:
URL: https://github.com/apache/arrow/pull/6725#issuecomment-649076794


   @sbinet could you assist with 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.

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




[GitHub] [arrow] wesm commented on pull request #6725: ARROW-8226: [Go] Implement 64 bit offsets binary builder

2020-06-24 Thread GitBox


wesm commented on pull request #6725:
URL: https://github.com/apache/arrow/pull/6725#issuecomment-649076694


   Hm, at a high level it seems like it might be better to have a separate set 
of LargeBinary types rather than try to pack both 32-bit and 64-bit into the 
same types. This means some code duplication (given Go's current 
generics/templates situation) but perhaps for the best



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:
us...@infra.apache.org