It was pulled out of the ADBC project so you can see an example at [1] (API changed slightly when ported though).
Yes, it'll bind one row of values at a time, and your description is correct. [1]: https://github.com/apache/arrow-adbc/blob/cf43e0cc2ae15ad0ce669b531d475ee218698100/java/driver/jdbc/src/main/java/org/apache/arrow/adbc/driver/jdbc/JdbcStatement.java#L160 -David On Wed, Jul 20, 2022, at 14:22, Gavin Ray wrote: > That JDBC PreparedStatement binding utility looks super useful! > I had one question about the behavior of it, if that's alright: > > The doc says: > > "Each call to next() will bind parameters >> from the next row of data, and then the application can execute the >> statement, call addBatch(), etc. as desired." > > > And shows the code: > > final JdbcParameterBinder binder = >> JdbcParameterBinder.builder(statement, root).bindAll().build(); > > > >> while (binder.next()) { >> statement.executeUpdate(); >> } > > > Could someone elaborate what happens here with some simple example > VectorSchemaRoot? > I'm having trouble following the meaning. Does this perform executeUpdate() > once for each row-wise set of column values? > > On Wed, Jul 20, 2022 at 1:41 PM Will Jones <will.jones...@gmail.com> wrote: > >> Attendees: >> >> - Jacob Wujciak-Jens >> - James Duong >> - Rok Mihevc >> - Raul Cumplido >> - Eduardo Ponce >> - Jeremy Parr-Pearson >> - Will Jones >> - Joris Van den Bossche >> >> Discussion >> >> Arrow 9.0.0 Release >> >> Increased capacity for crossbow, like 3x, including Macs. Devs are >> encouraged to use more crossbow runs to make sure their PRs keep master as >> release-able as possible. >> >> >> Also working on more caching improvements, but likely won’t make it in by >> release. >> >> There's been a large decline in passing nightly tests in recent days (see >> the Nightly Dashboard [1]). This is mostly caused by race conditions in the >> scanner (ARROW-17127 [2]). This issue is a blocker for release, but does >> not yet have any progress. >> >> We still have 8 blocker issues for release (see release dashboard [3]). >> Only 4 of them appear to be actively worked on, so more attention is needed >> on these issues. >> >> >> From monday onwards, there will be a feature freeze for the 9.0.0 release. >> The release managers will only cherry pick commits that fix blocker issues. >> Contributors should continue to merge stuff to master as normal; it will >> just not be included in release. >> >> One nightly failure is due to a known issue with protobuf ABI on MacOS. >> There is an upstream release coming soon that will fix it [4]. >> >> Any reviews that should be prioritized? David noted that the JDBC module in >> Java needs to be reviewed by additional maintainers [5]. Key question: Do >> we want to support this? >> Win32 PR >> >> James has been working on the Win32 PR fix [6]. Mostly build warnings being >> fixed. Focusing on 2017 32-bit MSVC. Most of the library code has been >> fixed; now fixing test cases. >> >> One failing test is the R ubuntu test. Rok noted it is likely unrelated as >> he is seeing elsewhere [7]. >> Flight SQL JDBC Contribution Update >> >> Apache side was scrutinizing the vote, but now that discussion is settled. >> Still waiting on one ICLA, which may have been submitted but gotten lost. >> This contribution likely won’t hit 9.0.0. >> >> >> [1] https://crossbow.voltrondata.com/ >> [2] https://issues.apache.org/jira/browse/ARROW-17127 >> [3] https://cwiki.apache.org/confluence/display/ARROW/Arrow+9.0.0+Release >> [4] https://github.com/protocolbuffers/protobuf/pull/10271 >> [5] https://github.com/apache/arrow/pull/13589 >> [6] https://github.com/apache/arrow/pull/13532 >> [7] https://github.com/apache/arrow/runs/7424773120?check_suite_focus=true >> >> >> >> On Tue, Jul 19, 2022 at 12:50 PM Ian Cook <i...@ursacomputing.com> wrote: >> >> > Hi all, >> > >> > Our biweekly sync call is tomorrow at 12:00 noon Eastern time. >> > >> > The Zoom meeting URL for this and other biweekly Arrow sync calls is: >> > https://zoom.us/j/87649033008?pwd=SitsRHluQStlREM0TjJVYkRibVZsUT09 >> > >> > Alternatively, enter this information into the Zoom website or app to >> > join the call: >> > Meeting ID: 876 4903 3008 >> > Passcode: 958092 >> > >> > Thanks, >> > Ian >> > >>
