Attendees: Matt Topol Will Jones David Li Joris Van den Bosche Eduardo Ponce Atoine Pitrou Jacob Wujciak Ivan Ogasawara Ashish Paliwal Niranda Perera
Discussion: - FlightSQL PR reviews David Li is inviting reviewers to two FlightSQL PRs. [1] "ARROW-7744: [Java][FlightRPC] JDBC Driver for Arrow Flight SQL" is a fairly large (24k lines) Java PR for those who enjoy such things. "[2] RFC: [C++][Java][FlightRPC] Substrait, transaction, cancellation for Flight SQL" adds Substrait to Flight SQL. Once interest dies down David will open a vote. - C++17 switch proposal A proposal was raised on the ML to switch to C++17 [3]. No objections on the call. - ARROW-16778: [C++] Fix win32 build and tests [4] Checking on the status of the PR. James added the necessary static casts. Arkadiy added other fixes. We should probably just set strict warnings raised by 32bit MSVC instead of adding many static casts. The counter point is that downstream projects would have to silence warnings too which they might not be able to do. One possible way forward would be for Arkadiy to adopt some changes from James' PR and shut down MSVC warnings. - Canonical extension types Proposal to add JSON logical type to Arrow [5] triggered another discussion about canonical extension types (older discussion here [7]). Minor point of disagreement is how the standardized namespace (e.g. org.apache.org.uuid, org.apache.arrow.uuid, ARROW:UUID, arrow.UUID) would look like. Some prior art at geo-arrow-spec [7]. - Arrow-cpp on conda-forge Unfortunately Ivan who proposed this point had to leave. There is a stalled discussion on his PR [8] to add arrow-c-glib to conda-forge that Ivan wants to revive. Currently there exists arrow-c-glib-feedstock [9]. - Splitting out sphinx docs per project component It's still something we'd want to do but Joris is lacking time to work on it. It would improve the experience of both docs contributors and users. The PR in question [10] and a preview example Joris made semi-manually [11]. Docs are currently built in CI and we could just copy them to a bucket so changes could be easily reviewed by contributors and reviewers. Ideally built docs would be uploaded into a bucket and a link would be posted to PR comments. Stale docs would be removed by bucket lifecycle policy. Jira [12]. - Ongoing CI development Jacob is working on enabling several new applications of the comment bot (e.g. labelling of PRs). Documentation build could be one of those applications. The idea is to trigger arbitrary AWS lambdas via the comments. [1] https://github.com/apache/arrow/pull/13800 [2] https://github.com/apache/arrow/pull/13492 [3] https://lists.apache.org/thread/9g14n3odhj6kzsgjxr6k6d3q73hg2njr [4] https://issues.apache.org/jira/browse/ARROW-16778 [5] https://lists.apache.org/thread/qxc1g7h9ow79qt6r7sqtgbj8mdbdgnhb [6] https://lists.apache.org/thread/3nls3222ggnxlrp0s46rxrcmgbyhgn8t [7] https://github.com/geopandas/geo-arrow-spec/blob/main/extension-types.md#concrete-examples-of-extension-type-metadata [8] https://github.com/conda-forge/staged-recipes/pull/19427 [9] https://github.com/conda-forge/arrow-c-glib-feedstock/ [10] https://github.com/apache/arrow/pull/11980 [11] https://jorisvandenbossche.github.io/arrow-docs-preview/html-splitted/developers/contributing.html [12] https://issues.apache.org/jira/browse/ARROW-12958 Rok
