alistaire47 commented on issue #35917: URL: https://github.com/apache/arrow/issues/35917#issuecomment-1581070740
As far as I can tell, we're installing duckdb from CRAN as a dep and it's not pinned, so yes, we're subject to breaking changes: https://github.com/voltrondata-labs/arrowbench/blob/ebfab3d5535a1a7ba8680be4d0394296b9b1a5ee/DESCRIPTION#L19 It's worth running against 0.6.0 and 0.8.0 and seeing if we can reproduce the issue. Pinning isn't common in R `DESCRIPTION`s (current best-practice is using [renv](https://rstudio.github.io/renv/articles/renv.html) to make a lock file), but seems like the quick solution here if this is actually the problem (though if it results in building duckdb from source instead of getting a binary, it could add ~half an hour to runtimes. But maybe we're already doing that in most cases?). If we decide to update instead, we'll likely need to clear the dataset caches from the bare-metal machines. Elena has done this for us before, but I'm not totally sure how. Maybe we should make a little triggerable buildkite job to do this as necessary? -- 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]
