+1 for this, hoping that I can get funding to attend too! Lol
--Matt
On Thu, Mar 6, 2025, 9:07 AM Antoine Pitrou wrote:
>
> Hi JB,
>
> This is a great idea, I like it.
>
> +1 for doing this in Europe, also less risky these days given the
> geopolitical context.
>
> Half a day is probably too sh
Just wanted to chime in here:
The builders and the CSV reader are currently explicitly NOT goroutine
safe, there are no locks or checks in them to prevent race conditions.
In the sample code you have above Gus, you need to add a call to
record.Retain() before the `go func()` call. This is because
Sorry for the VERY late reply here, but there is an ongoing PR being worked
on for Avro support in the Go Arrow libs [1]. Feel free to watch /
contribute / test out that branch while we iron out the specifics and get
it ready.
--Matt
[1]: https://github.com/apache/arrow/pull/37115
On Sun, Sep 3,
In addition to the links that Bryce provided, the arrow Go library *does*
support marshalling a record batch into JSON if that's desired. You should
be able to simply pass a record batch to the json.Marshal functions.
That said, the ipc route that Bryce linked would be much more efficient.
On Thu
Hey Wyatt,
Looking at the code, it's not `NewRecord` that calls mem.Allocate, it's the
call to `Append` which does the allocating.
The reason why `builder.cap` is zeroed out on reset for array Builders is
because there's no way to know that the array has been released and that it
is safe to re-us