Attendees: Neal Richardson François Saint-Jacques Micah Kornfield Ravindra Pindikura Ben Kietzman John Muehlhausen
Micah raised several issues: * C++ status: 2 PRs: 1. make status pluggable, clean up error codes ( https://github.com/apache/arrow/pull/4484). Antoine has been reviewing, but it would be great to get feedback if anyone has any other concerns. Wes discussed adding an assertion that the size of the status struct isn't changed. Discuss concern that might have an effect for Plasma, Gandiva. 2. StatusOr (https://github.com/apache/arrow/pull/4501). Wes in favor, discussed deprecation plan * Avro in C++ ( https://lists.apache.org/thread.html/eba58f3242be08e50cd6052e6d6c1dcb008c449bf4c94d4dcb26c0e1@%3Cdev.arrow.apache.org%3E, https://issues.apache.org/jira/browse/ARROW-1209 and related issues). Strategy of copying from Avro ( https://github.com/apache/avro/tree/master/lang/c%2B%2B) and then rework. Ravindra discussed performance and codegen. * 1.0, and what that means for forward compatibility. Should we have encodings and compression built in, and checksumming? If we call 1.0 does that limit our ability to make those changes? Wes: implementations should be robust to structures they don't recognize. Implementation question, document is what in 1.0 and build that into writers so they know how to write in a way that is compatible. Digression/discussion re: encodings, make a different kind of record batch? John discussed how they deal with compression at lower level, concern with piecewise decompression. To start the discussion of what guarantees 1.0 means, what is required of implementations, how we'll handle certain cases, etc., Micah will start a google doc and circulate on the mailing list. * Seeking more review on dictionary type in java ( https://lists.apache.org/thread.html/d8d2c1ef7135a64f56c3eed465872d99c0c639bf78cf8bee3abd94b7@%3Cdev.arrow.apache.org%3E, https://issues.apache.org/jira/browse/ARROW-3396) Neal raised issue of preparation for the 0.14 release, encouraging everyone to turn their attention to resolving issues that are critical for release. There are a number of blockers: see https://cwiki.apache.org/confluence/display/ARROW/Arrow+0.14.0+Release. Wes raised concern that our packaging is probably broken and that needs to be fixed before we can release. On a related note, Ursa Labs is hiring a Build Automation Engineer to support the Arrow project's continuous-integration and packaging infrastructure. Anyone interested should see https://hire.withgoogle.com/public/jobs/rstudiocom/view/P_AAAAAACAAJZHZE3lvPT2nK On Tue, Jun 11, 2019 at 10:34 AM Neal Richardson < neal.p.richard...@gmail.com> wrote: > Hi everyone, > Reminder that the biweekly Arrow call is tomorrow at > https://meet.google.com/vtm-teks-phx. All are welcome to join. Given the > current discussions on the list, including around timing and content of > upcoming releases, there's lots to chat about. > > Notes will be sent out to the mailing list afterwards. > > Neal >
