Hello Jim and Sebastien, > As far as I know, List<Struct<...>> hasn't been implemented yet. These are > some previous discussions on the Arrow and Parquet mailing lists.
This may be a statement that lead to a bit of confusion. I want to clarify a bit here: * Arrow C++/Python supports dealing with List<Struct<..>>. * The Parquet C++ Arrow interface can either deal with List<..> or Struct<..> be they cannot be mixed at the moment in a single type. This limitation is only due to the implementation of the Parquet<->Arrow interface. Arrow itself can deal with these types and Parquet also supports these types. Just the connection between both currently misses the necessary translation code. > but the Go package, AFAICT, is even missing support for structs (and it's a > pure-Go package, reimplementing things from first principles). > hence my question on the amount of work needed to implement (at least) > support for structs. As the C++ maintainer, I would say that implementing struct is not extremely complicated. My Go experience is rather limited and I'm not aware what the situation of templates or generics is in Go. Struct types will depend on the fact that you would implement certain things for the Struct itself but mainly have some generic delegation code that calls the underlying primitive types. Uwe On Tue, Jun 19, 2018, at 9:21 AM, Sebastien Binet wrote: > hi Jim, > > (happy to see you there!) > > On Mon, Jun 18, 2018 at 4:43 PM Jim Pivarski <jpivar...@gmail.com> wrote: > > > > > - > > > > http://mail-archives.apache.org/mod_mbox/parquet-dev/201801.mbox/%3C4221159.JjGKrUjAfh@gudok6%3E > > - > > > > https://lists.apache.org/thread.html/45179fd4023764f8303c6dee57a9b65afcb660ab0c5d60842caf30d9@%3Cdev.arrow.apache.org%3E > > - > > > > http://mail-archives.apache.org/mod_mbox/arrow-dev/201805.mbox/%3CCAJEf=x6ouiagp5lnfxfftem_yry0jxazu7ysfv9qh9v14y_...@mail.gmail.com%3E > > > > > thanks for the pointers. > > -s
