Given the upcoming Snowflake Summit talk on ADBC with the Snowflake driver, and potential deadlock condition addressed by [1], it might make sense for us to do a v0.5.1 patch release of ADBC.
Unfortunately I only discovered the issue just as the voting for 0.5.0 closed and the release was finalized, otherwise I would have brought it up during the voting for that release. In this case, we are likely going to have a large influx of users after the conference coming to try out the Snowflake ADBC driver and I don't want them to end up with a bad experience if they hit a deadlock when testing with very large result sets. What does everyone else think? -Matt [1]: https://github.com/apache/arrow-adbc/pull/828
