CurtHagenlocher commented on issue #1358: URL: https://github.com/apache/arrow-adbc/issues/1358#issuecomment-2303587052
Okay, so instead of returning a different status, we'd return `ADBC_STATUS_OK` and set the `release` on `schema` and `out` (if supplied) to NULL? That works. I gather from another issue that we're gearing up for a release soon, and I'm a bit embarrassed to admit that the release schedule is completely opaque to me. Is it the case that both the core Arrow project and the ADBC subproject are on a bimonthly release cadence, but on alternating months? Regardless, it seems that there's almost certainly not enough time to get this change in for the very next release, but I'd like to try to drive this item and a bunch of other API changes on the backlog and combine them into a 1.2 version of the spec for the subsequent release. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
