Micah is correct, the arrjson package is used for the internal integration testing using the specific JSON format for that integration testing which is not likely what Users would want when converting Arrow to JSON.
There is not currently a recommended way to serialize an instance of arrow.Table to JSON because there is not standardized external format expected as JSON for arrow to my knowledge. Having arrjson be internal is intentional due to it being for the internal integration testing. -----Original Message----- From: Micah Kornfield <emkornfi...@gmail.com> Sent: Wednesday, April 21, 2021 11:19 PM To: dev <dev@arrow.apache.org> Subject: Re: [Go] expose ability to write arrow.Table to JSON > I was wondering why `arrjson` is kept as an internal package within go/arrow. I think this is probably what is used for internal integration testing, we have specific JSON format that is expected, that needs to free to evolve and probably isn't what users are looking for. > Is there a different recommended way to serialize an instance of `arrow.Table` to JSON? afaict, using `arrjson.Writer` seems like a great way to do this, but it isn't possible to depend on it as an external user, because of it residing within the `.../internal/...` path. Sorry I don't know the answer to this, but I would guess there isn't anything currently in the Go package for this. On Wed, Apr 21, 2021 at 6:45 PM Agam Brahma <agam.bra...@gmail.com> wrote: > Hi all, > > I was wondering why `arrjson` is kept as an internal package within > go/arrow. > > Is there a different recommended way to serialize an instance of > `arrow.Table` to JSON? afaict, using `arrjson.Writer` seems like a > great way to do this, but it isn't possible to depend on it as an > external user, because of it residing within the `.../internal/...` path. > > Any pointers are much appreciated. > > Thanks, > Agam > > > >
